From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
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 20:50:44 |
Message-ID: | 10155.1303505444@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
There's still the problem of whether you can invoke operations such as
VACUUM from such an SP. I think we'd want to insist that they terminate
the current xact, which is perhaps not too cool.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-04-22 20:55:30 | Re: fsync reliability |
Previous Message | Tom Lane | 2011-04-22 20:32:30 | Collation patch's handling of wcstombs/mbstowcs is sheerest fantasy |