On Wed, Mar 23, 2016 at 8:21 AM, Merlin Moncure <mmonc...@gmail.com> wrote: > I'm not understanding the objection at all. You have N client > sessions connecting to the database that all utilize the same named > prepared statement. A typical pattern is for the application to > prepare them all upon startup, but currently each PREPARE needs to be > wrapped with an exception handler in case someone else prepared it > first. Having an IF NOT EXISTS decoration simplifies this. This can > happen both inside and outside of connection pooling scenarios.
I'm walking that back a bit -- this is only interesting in pooler scenarios, especially pgbouncer where you have no way of knowing if the statement is created or not. Of course, you can always re-prepare them following a discard but that's quite pessimal in many cases. Still, I've often wanted this exact feature. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
