Re: Creating unique or "internal-use-only" column names (ColumnRef) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Creating unique or "internal-use-only" column names (ColumnRef)
Date
Msg-id 9037.1441636823@sss.pgh.pa.us
Whole thread Raw
In response to Re: Creating unique or "internal-use-only" column names (ColumnRef)  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Creating unique or "internal-use-only" column names (ColumnRef)  (Peter Moser <pitiz29a@gmail.com>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Move DTK_ISODOW DTK_DOW and DTK_DOY to be type UNITS rather than
Next
From: Masahiko Sawada
Date:
Subject: Re: Freeze avoidance of very large table.