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

Re: Continue transactions after errors in psql

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>,pgsql-patches(at)postgresql(dot)org
Subject: Re: Continue transactions after errors in psql
Date: 2005-01-28 15:11:34
Message-ID: 1106925095.31694.4670.camel@camel (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Fri, 2005-01-28 at 04:46, Christopher Kings-Lynne wrote:
> > I've attached a revised patch which fixes the problem, however I'm sure there 
> > is a better way.  Thanks to Neil for putting up with me on irc :-)
> 
> How about calling the savepoint pg_psql_savepoint instead, that way it 
> follows our 'don't begin things with pg_' philosophy.
> 

I was actually thinking of calling it something like
pg_<xact-start-time> thinking that would be pretty unique within a
transaction, though having a specific documented name seemed ok too. 

Robert Treat
-- 
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL


In response to

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2005-01-28 15:52:54
Subject: Re: strange 'vacuum verbose analyze' behaviour
Previous:From: Tom LaneDate: 2005-01-28 15:00:21
Subject: Re: strange 'vacuum verbose analyze' behaviour

pgsql-patches by date

Next:From: Ed LoehrDate: 2005-01-28 17:30:20
Subject: Re: dbsize patch
Previous:From: Tom LaneDate: 2005-01-28 14:57:23
Subject: Re: [PATCHES] Merge pg_shadow && pg_group -- UNTESTED

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