| From: | Marco <marcojoemontagna(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | [WIP] Reduce likelihood of fdw prepared statement collisions |
| Date: | 2021-01-29 08:14:58 |
| Message-ID: | CABfz-yzDW1PcRWd=KVn+DSE59MpFFm+AHu1PTxNOozLrkirHjQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi All,
I realize using foreign data wrappers with transaction pooling may not be
strictly supported, but for the most part they work. I am however
occasionally noticing errors stemming from the prepared statement names
created by the fdw modify code colliding between sessions/DBs.
Would the development team be open to a patch which somehow makes this less
likely? Something like the attached patch works, but probably isn't ideal?
Perhaps there is a better unique identifier I can use here. I am very new
to the postgres codebase.
Best
*Marco Montagna*
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Reduce-likelihood-of-fdw-prepared-statement-collisio.patch | text/x-patch | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-01-29 08:34:47 | Re: Snapbuild woes followup |
| Previous Message | Masahiko Sawada | 2021-01-29 08:05:06 | Re: Key management with tests |