Re: "stored procedures" - use cases?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "stored procedures" - use cases?
Date: 2011-05-10 01:21:07
Message-ID: 4DC89303.9070006@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/09/2011 08:20 PM, Bruce Momjian wrote:
> Tom Lane wrote:
>> Peter Eisentraut<peter_e(at)gmx(dot)net> writes:
>>> On mån, 2011-04-25 at 14:35 -0500, Kevin Grittner wrote:
>>>> (1) All the \d commands in psql should be implemented in SPs so
>>>> that they are available from any client, through calling one SP
>>>> equivalent to one \d command.
>>> You don't need stored procedures with special transaction behavior for
>>> this.
>> No, but what you *would* need is the ability to return multiple result
>> sets from one call. Even then, you could not exactly duplicate the
>> current output of \d; but you could duplicate the functionality.
> Oh, good point. Thanks.

Multiple resultsets in one call would be a good thing, though, no?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-05-10 01:43:30 Re: Formatting Curmudgeons WAS: MMAP Buffers
Previous Message Alvaro Herrera 2011-05-10 01:09:50 Re: Formatting Curmudgeons WAS: MMAP Buffers