Support prepared statements

[citus-github-bot]

Issue by jasonmp85
Thursday Sep 03, 2015 at 05:00 GMT
Originally opened as citusdata/pg_shard#140

---

Now that we've addressed this in CitusDB, we want to get it into pg_shard as well. We know how to do prepared statements for queries, but pg_shard must support modifications as well. Adding this support will remove a ton of friction from database adapters (such as Psycopg in Python, pg in Ruby, or the JDBC adapters in Java).

[citus-github-bot]

Comment by makkesk8
Wednesday Jan 06, 2016 at 23:09 GMT

---

+1

[citus-github-bot]

Comment by awolfe-silversky
Friday Jan 15, 2016 at 19:22 GMT

---

+1

[ozgune]

Citus 5.0 comes with PREPARE, and we have three open issues around improving our PREPARE support.

• Issue Support for PREPARE statements with parameters #306 relates adding support for parameterized PREPARE queries
• Issue Invalidate cached plans for PREPARE statements.  #127 relates to invalidating cached plans when shard placements change
• Issue Memory problem with PREPAREd statements and task-tracker executor #256 relates to memory allocation issues with PREPARE queries that use the task tracker executor

@jasonmp85, I'm happy to update this issue in pg_shard and close it in this repository. What do you think?

[jasonmp85]

I'm happy to update this issue in pg_shard and close it in this repository. What do you think?

I think that's a great pattern. In fact, I think we should announce the Citus 5.0 release on various pg_shard issues and close them.