Re: --single-transaction doc clarification - Mailing list pgsql-patches

From Simon Riggs
Subject Re: --single-transaction doc clarification
Date
Msg-id 1162248999.11568.379.camel@silverbirch.site
Whole thread Raw
In response to Re: --single-transaction doc clarification  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: --single-transaction doc clarification  (Neil Conway <neilc@samurai.com>)
List pgsql-patches
On Mon, 2006-10-30 at 17:32 -0500, Tom Lane wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > Clarification of when it's not appropriate to use this option.
>
> I think it's a fairly bad idea to try to enumerate the commands that
> can't be used in a transaction block here, because there is no way
> that we will remember to keep such a list up-to-date.  Why not just
> say "It won't work for commands that can't be used in a transaction
> block"?

I agree, but such a comment immediately begs the question: What is the
list of commands this applies to? I was surprised how long a list it was
myself, hence the patch.

(Checks)...The man pages for VACUUM, CREATE TABLESPACE, CLUSTER and
REINDEX DATABASE don't mention they are not allowed inside a transaction
block at all, so I'm not sure if doing it the other way around helps
with maintaining docs...

I prefer useful info rather than hidden gotchas, even if the list might
possibly be < 100% exactly correct. At least we can say we tried.

--
  Simon Riggs
  EnterpriseDB   http://www.enterprisedb.com



pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: --single-transaction doc clarification
Next
From: "Simon Riggs"
Date:
Subject: Re: [HACKERS] WAL logging freezing