From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Hans Buschmann <buschmann(at)nidsa(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Assorted improvements in pg_dump |
Date: | 2021-10-26 22:31:05 |
Message-ID: | 177444.1635287465@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> I guess we could move the prepared-statement handling into a query execution
> helper. That could then use a hashtable or something similar to check if a
> certain prepared statement already exists. That'd then centrally be extensible
> to deal with multiple connects etc.
That seems like more mechanism than is warranted. I tried it with a
simple array of booleans, and that seems like not too much of a mess;
see revised 0006 attached.
(0001-0005 are the same as before; including them just to satisfy
the cfbot.)
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
0001-fix-component-masking-2.patch | text/x-diff | 47.1 KB |
0002-rethink-ACL-handling-2.patch | text/x-diff | 121.1 KB |
0003-move-unsafe-function-calls-2.patch | text/x-diff | 10.0 KB |
0004-bulk-queries-2.patch | text/x-diff | 74.2 KB |
0005-fix-toast-sched-2.patch | text/x-diff | 4.6 KB |
0006-prepare-repeated-queries-3.patch | text/x-diff | 34.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-10-26 22:45:36 | Re: Feature request for adoptive indexes |
Previous Message | Tom Lane | 2021-10-26 22:16:34 | Re: allowing "map" for password auth methods with clientcert=verify-full |