Postgres Pro
Downloads
Home   >   mailing lists

Re: why can't plpgsql return a row-expression? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: why can't plpgsql return a row-expression?
Date
Msg-id CA+TgmoYqoeq9vojzPOWvXsJZHVL0xGBeW=aUyNMH1kMkvMBZyg@mail.gmail.com
Whole thread Raw
In response to Re: why can't plpgsql return a row-expression?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: why can't plpgsql return a row-expression?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Thu, Dec 6, 2012 at 1:36 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm against putting I/O coercion semantics into tupconvert, period.  Ever.
> If plpgsql wants that behavior rather than something more consistent
> with the rest of the system, it needs to implement it for itself.

I'm sure that can be done.  I don't think anyone is objecting to that,
just trying to get useful behavior out of the system.

Are you going to commit a stripped-down version of the patch?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: ALTER TABLE ... NOREWRITE option
Next
From: Andres Freund
Date:
Subject: Re: How to check whether the row was modified by this transaction before?