Horton

Re: Inadequate infrastructure for NextValueExpr

Thomas Munro <thomas.munro@enterprisedb.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>, Kevin Grittner <kgrittn@gmail.com>, Andrew Gierth <andrew@tao11.riddles.org.uk>
Date: 2017-08-17T22:47:23Z
Lists: pgsql-hackers 
On Fri, Jul 14, 2017 at 1:46 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> [...]
> T_NamedTuplestoreScan can be produced by outfuncs.c with tagname
> NAMEDTUPLESTORESCAN but that tagname is not recognized by readfuncs.c
> [...]
>
> That revealed a defect in commit
> 18ce3a4ab22d2984f8540ab480979c851dae5338 which I think should be
> corrected with something like the attached, though I'm not sure if
> it's possible to reach it.

Adding Kevin and Andrew G.  Thoughts on whether this is a defect that
should be corrected with something like
read-namedtuplestorescan.patch?

-- 
Thomas Munro
http://www.enterprisedb.com

Commits

  1. Code review for NextValueExpr expression node type.

  2. Add infrastructure to support EphemeralNamedRelation references.