| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vote totals for SET in aborted transaction |
| Date: | 2002-04-29 17:47:54 |
| Message-ID: | 1020102474.27495.46.camel@taru.tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2002-04-29 at 18:20, Tom Lane wrote:
> Thomas Lockhart <lockhart(at)fourpalms(dot)org> writes:
> > Rather than dismissing this out of hand, try to look at what it *does*
> > enable. It allows developers to tune specific queries without having to
> > restore values afterwards. Values or settings which may change from
> > version to version, so end up embedding time bombs into applications.
>
> I think it's a great idea.
So do I.
And I also think that this will solve the original issue, which iirc was
rolling back SET TIMEOUT at ABORT.
If we have LOCAL SET, there is no need to have any other mechanism for
ROLLING BACK/COMMITing SET's - SET and DML can be kept totally separate,
as they should be based on fact that SET does not directly affect data.
--------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-29 18:05:39 | Folding variable.c into the GUC structure, redux |
| Previous Message | Hannu Krosing | 2002-04-29 17:39:25 | Re: Vote totals for SET in aborted transaction |