From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
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>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: "stored procedures" |
Date: | 2011-04-22 21:52:09 |
Message-ID: | BANLkTin-ZArXPb1gDNn_qdQY3R0FX_cq=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 22, 2011 at 3:50 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
>> On Fri, Apr 22, 2011 at 1:28 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>>> It would probably be more reasonable and feasible to have a setup where
>>> you can end a transaction in plpgsql but a new one would start right
>>> away.
>
>> ya, that's an idea.
>
> Yeah, that's a good thought. Then we'd have a very well-defined
> collection of state that had to be preserved through such an operation,
> ie, the variable values and control state of the SP. It also gets rid
> of the feeling that you ought not be in a transaction when you enter
> the SP.
hm, another neat thing about this is that it skirts the unfortunate
confusion between sql 'begin' and plpgsql 'begin'...
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-04-22 22:00:00 | Re: "stored procedures" |
Previous Message | Bruce Momjian | 2011-04-22 21:34:08 | Re: Patch for pg_upgrade to turn off autovacuum |