Re: Creating unique or "internal-use-only" column names (ColumnRef)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Moser <pitiz29a(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Creating unique or "internal-use-only" column names (ColumnRef)
Date: 2015-09-07 14:40:23
Message-ID: 9037.1441636823@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 09/07/2015 09:28 AM, Alvaro Herrera wrote:
>> This seems pretty much the same as a junk attribute, if I understand you
>> correctly. I suggest given a look at how those work.

> Is that actually documented anywhere much?

I don't think there's much besides a code comment here and there.
Grepping for functions that touch the "resjunk" field of TargetListEntries
should give you the lay of the land.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2015-09-07 15:18:16 Re: Freeze avoidance of very large table.
Previous Message Tom Lane 2015-09-07 14:33:22 Re: [COMMITTERS] pgsql: Move DTK_ISODOW DTK_DOW and DTK_DOY to be type UNITS rather than