Re: [PATCH] Docs: Make notes on sequences and rollback more obvious

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Craig Ringer" <ringerc(at)ringerc(dot)id(dot)au>
Cc: "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Docs: Make notes on sequences and rollback more obvious
Date: 2012-08-07 13:45:35
Message-ID: 5020D5AF0200002500049461@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> 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.
>>
>> Some kind of hint that there are execptions is IMO very
>> important. I'm not sure what the best form for it to take is.
>
> I'm not sure, either. Maybe we should avoid blanket statements
> and just say something like:
>
> Note: Some operations on sequences are non-transactional and will
> not be rolled back on transaction abort. See <xref>.

I also think it's a problem that one can get through the entire
"Concurrency Control" chapter (mvcc.sgml) without a clue that
sequences aren't transactional. I think maybe a mention in the
Introduction section of that chapter with a <ref> would be
appropriate.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-08-07 14:01:40 Re: -Wformat-zero-length
Previous Message Magnus Hagander 2012-08-07 13:22:16 Pg_ctl promote -- wait for slave to be promoted fully ?