From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Docs: Make notes on sequences and rollback more obvious |
Date: | 2012-08-07 17:13:34 |
Message-ID: | 20120807171334.GB1697@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 07, 2012 at 03:59:42PM +0800, Craig Ringer wrote:
> On 08/07/2012 02:27 AM, Robert Haas wrote:
> >I did not commit the advanced.sgml changes.
>
> That's arguably the most important point to raise this. The most
> recent question came from someone who actually bothered to RTFM and
> believed based on the advanced-transactions page that rollback rolls
> *everything* back.
Perhaps we should see about correcting that misapprehension. When
PostgreSQL does any irreversible process
<http://en.wikipedia.org/wiki/Irreversible_process> such as
incrementing a sequence, writing a file, sending an email, etc., it
can't be rolled back. Might it be useful to find those irreversible
operations we document and mark same?
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-08-07 17:24:01 | Re: Re: BUG #6742: pg_dump doesn't convert encoding of DB object names to OS encoding |
Previous Message | Bruce Momjian | 2012-08-07 17:10:52 | pg_upgrade bug in Windows on PG 9.2 |