Re: Centralizing protective copying of utility statements
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org
Date: 2021-06-18T02:26:00Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > The DECLARE CURSOR case in ExplainOneUtility() does a copy of a Query. > Perhaps a comment should be added to explain why a copy is still > required? I did add a comment about that in the v2 patch --- the issue is the call path for EXPLAIN EXECUTE. regards, tom lane
Commits
-
Avoid scribbling on input node tree in CREATE/ALTER DOMAIN.
- f172438ef6ff 10.18 landed
- b2c740c426da 12.8 landed
- 4b8b3562e1e6 11.13 landed
- 1a3d30255a4e 9.6.23 landed
- 102f31a208b8 13.4 landed
-
Centralize the logic for protective copying of utility statements.
- 7c337b6b527b 14.0 landed