| From: | Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
|---|---|
| To: | <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Subject: | NOT EXIST for PREPARE |
| Date: | 2016-03-22 09:41:43 |
| Message-ID: | a6e0672d-a547-48bb-9451-c952ddb161f4@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello hackers.
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?
Thanks.
--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2016-03-22 09:44:14 | Re: multivariate statistics v14 |
| Previous Message | Tomas Vondra | 2016-03-22 09:23:23 | Re: multivariate statistics v14 |