On Tue, Mar 22, 2016 at 10:01 AM, Andres Freund <and...@anarazel.de> wrote: > > Hi, > > > On 2016-03-22 12:41:43 +0300, Yury Zhuravlev wrote: > > Do I understand correctly the only way know availability PREPARE it will > > appeal to pg_prepared_statements? > > I think this is not a good practice. In some cases, we may not be aware of > > the PREPARE made (pgpool). Moreover, it seems popular question in the > > Internet: http://stackoverflow.com/questions/1193020/php-postgresql-check-if-a-prepared-statement-already-exists > > > > What do you think about adding NOT EXIST functionality to PREPARE? > > Not very much. If you're not in in control of the prepared statements, you > can't be sure it's not an entirely different statement. So NOT EXISTS > doesn't really buy you anything, you'd still need to compare the > statement somehow. >
You're correct, but IMHO it should be used when you have control of prepared statement... isn't it analogous to CREATE TABLE IF NOT EXISTS?? -- Fabrízio de Royes Mello Consultoria/Coaching PostgreSQL >> Timbira: http://www.timbira.com.br >> Blog: http://fabriziomello.github.io >> Linkedin: http://br.linkedin.com/in/fabriziomello >> Twitter: http://twitter.com/fabriziomello >> Github: http://github.com/fabriziomello
