Re: "stored procedures" - use cases?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 00:20:06
Message-ID: 201105100020.p4A0K6v11828@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > On mn, 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.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-05-10 01:09:50 Re: Formatting Curmudgeons WAS: MMAP Buffers
Previous Message Bruce Momjian 2011-05-10 00:19:04 Re: "stored procedures" - use cases?