From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Postgres hackers <pgsql-hackers@postgresql.org>
Subject: Re: pgsql: Remove absolete function TupleDescGetSlot().
Date: Wed, 26 Sep 2018 12:41:38 +0900
Message-ID: <20180926034138.GI1659@paquier.xyz> (raw)
In-Reply-To: <20180926014251.zrn27ljtqlqjzswx@alap3.anarazel.de>
References: <E1g4wv3-0001Q0-8n@gemulon.postgresql.org>
<20180926000413.GC1659@paquier.xyz>
<20180926001038.fh7rrhrqrwvpu43t@alap3.anarazel.de>
<20180926013851.GG1659@paquier.xyz>
<20180926014251.zrn27ljtqlqjzswx@alap3.anarazel.de>
On Tue, Sep 25, 2018 at 06:42:51PM -0700, Andres Freund wrote:
> My point is that FuncCallContext->slot isn't actually all that related
> to TupleDescGetSlot() and could be used entirely independently.
That's fair. Why not just replacing the existing comment with something
like "slot can be used in your own context to store tuple values,
useful in the context of user-defined SRFs"? Just my 2c.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, andres@anarazel.de, pgsql-hackers@postgresql.org
Subject: Re: pgsql: Remove absolete function TupleDescGetSlot().
In-Reply-To: <20180926034138.GI1659@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox