Horton

Re: Extending outfuncs support to utility statements

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org
Date: 2022-09-26T14:46:49Z
Lists: pgsql-hackers 
On 22.09.22 23:21, Tom Lane wrote:
> Anyway, this is a bit far afield from the stated topic of this
> thread.  I think we should commit something approximately like
> what I posted and then start a new thread specifically about
> what we'd like to do about utility commands in new-style SQL
> functions.

Right, I have committed everything and will close the CF entry.  I don't 
have a specific idea about how to move forward right now.

Commits

  1. Avoid copying undefined data in _readA_Const().

  2. Enable WRITE_READ_PARSE_PLAN_TREES of rewritten utility statements

  3. Implement WRITE_READ_PARSE_PLAN_TREES for raw parse trees

  4. Don't lose precision for float fields of Nodes.

  5. Fix write/read of empty string fields in Nodes.

  6. Add read support for some missing raw parse nodes

  7. Fix reading of BitString nodes

  8. Fix reading of most-negative integer value nodes