From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: --single-transaction doc clarification |
Date: | 2006-10-31 17:27:27 |
Message-ID: | 20061031172726.GI11985@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, Oct 30, 2006 at 07:18:04PM -0500, Neil Conway wrote:
> On Mon, 2006-10-30 at 22:56 +0000, Simon Riggs wrote:
> > The man pages for VACUUM, CREATE TABLESPACE, CLUSTER and
> > REINDEX DATABASE don't mention they are not allowed inside a transaction
> > block at all
>
> That should be fixed, I think. Once that is done, I think it's
> sufficient to just say that --single-transaction won't work for commands
> that can't be executed in a transaction block.
"What commands aren't allowed in a transaction?" is still a logical
question to ask though, so it would be nice if we had such a list
hanging around.
Is there a standard way these commands test to see if they're in a
transaction block? If there is, perhaps something could be created that
would pull that info out of the code so that we didn't have to maintain
the list by hand. It might also be possible to do this with some SGML
magic.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-10-31 17:55:46 | Re: [HACKERS] Case Preservation disregarding case |
Previous Message | Chuck McDevitt | 2006-10-31 17:13:31 | Re: [HACKERS] Case Preservation disregarding case |
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2006-10-31 19:49:27 | Re: [HACKERS] WAL logging freezing |
Previous Message | Tom Lane | 2006-10-31 16:23:40 | Re: [HACKERS] WAL logging freezing |