Re: Is temporary functions feature official/supported? Found some issues with it.
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alexey Bashtanov <bashtanov@imap.cc>, pgsql-bugs@postgresql.org, mmitar@gmail.com
Date: 2019-01-04T15:43:37Z
Lists: pgsql-bugs
On 2019-Jan-04, Michael Paquier wrote: > That should not be allowed to commit directly. I think that we should > just add a new value for MyXactFlags which tracks the transaction > where the temporary namespace has been created, and generate an error > if trying to use 2PC in this case. That implies that a 2PC transaction will fail if it's run in a session for which the temp namespace doesn't previously exist. I think it's a fairly ugly failure mode, and one that normal testing will not catch because it'll occur very rarely. An app that detects this problem at run time will have to create a random temp object, commit normally, then re-run the 2PC transaction from the start ... a lot of code to deal with something that shouldn't happen in the first place. I wonder if we can somehow create the temp schema in a way that makes it immediately visible to everyone, and not depend on the commit status of the creating transaction -- say mark the tuple with xmin=frozenXid or something like ugly that. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Restrict the use of temporary namespace in two-phase transactions
- b15160bc716e 10.7 landed
- 3e4fdb3bc0dc 11.2 landed
- c5660e0aa52d 12.0 landed