Skip site navigation (1) Skip section navigation (2)

Re: --single-transaction doc clarification

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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)

In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2006-10-31 17:55:46
Subject: Re: [HACKERS] Case Preservation disregarding case
Previous:From: Chuck McDevittDate: 2006-10-31 17:13:31
Subject: Re: [HACKERS] Case Preservation disregarding case

pgsql-patches by date

Next:From: Gregory StarkDate: 2006-10-31 19:49:27
Subject: Re: [HACKERS] WAL logging freezing
Previous:From: Tom LaneDate: 2006-10-31 16:23:40
Subject: Re: [HACKERS] WAL logging freezing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group