| From: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Vince Vielhaber <vev(at)michvhf(dot)com>, Mike Mascari <mascarm(at)mascari(dot)com>, Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vote totals for SET in aborted transaction |
| Date: | 2002-04-26 08:46:04 |
| Message-ID: | 15561.5068.40814.285016@kelvin.csl.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marc G. Fournier writes:
> Myself, I wonder why Oracle went the route they went ... does anyone have
> access to a Sybase / Informix system, to confirm how they do it? Is
> Oracle the 'odd man out', or are we going to be that? *Adding* something
> (ie. DROP TABLE rollbacks) that nobody appears to have is one thing ...
> but changing the behaviour is a totally different ..
FWIW, Ingres also doesn't rollback SET. However all its SET
functionality is the sort of stuff you wouldn't assume to rollback:
auto-commit
connection
journaling
logging
session
work locations
maxidle
You cannot do something sane like modify the date output through SET.
Lee.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2002-04-26 11:33:30 | Re: WAL -> Replication |
| Previous Message | Shad | 2002-04-26 08:37:50 | PSQL \x \l command issues |