[WIP] Reduce likelihood of fdw prepared statement collisions - Mailing list pgsql-hackers

From Marco
Subject [WIP] Reduce likelihood of fdw prepared statement collisions
Date
Msg-id CABfz-yzDW1PcRWd=KVn+DSE59MpFFm+AHu1PTxNOozLrkirHjQ@mail.gmail.com
Whole thread Raw
List 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

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Key management with tests
Next
From: Amit Kapila
Date:
Subject: Re: Snapbuild woes followup