Re: Proposal: TABLE functions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Proposal: TABLE functions
Date
Msg-id 24640.1171033329@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposal: TABLE functions  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
List pgsql-hackers
"Pavel Stehule" <pavel.stehule@hotmail.com> writes:
> it can by more simple than I though. I need only one flag, and if its true 
> then I don't create language variables for OUT params. But I need one next 
> column in pg_proc.

I thought you said this was just syntactic sugar for capabilities we
already had?

> Currently a lot of columns in pg_proc is bool. What about one binary columns 
> for other options? I hope so next versions can support autonomous 
> transaction, which need flag too.

I think stored procedures of that sort aren't functions at all, and
probably don't belong in pg_proc.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCHES] plpgsql, return can contains any expression
Next
From: Tom Lane
Date:
Subject: Re: Variable length varlena headers redux