| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Yury Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Subject: | Re: NOT EXIST for PREPARE |
| Date: | 2016-03-22 13:01:18 |
| Message-ID: | 20160322130118.GI3790@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2016-03-22 13:03:06 | Re: Proposal: Generic WAL logical messages |
| Previous Message | Andres Freund | 2016-03-22 12:59:57 | Re: Speed up Clog Access by increasing CLOG buffers |