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

Re: Continue transactions after errors in psql

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-patches(at)postgresql(dot)org
Subject: Re: Continue transactions after errors in psql
Date: 2005-02-02 03:49:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Hash: SHA1
> Do you think it's better to create a server-side function or
> handle that in the client? How hard would it be to implement
> such a function? And what should it return? Only the name of
> the current top savepoint?
I think handled on the client. Otherwise, this will not work
for 8.0 and I'd like to see it able to do so. I tbink the
logic presented so far is good: I'll work on getting a new
patch out as soon as I can.
Still, a server-side function would eventually be nice, perhaps
have it return a setof savepoint names in order, allowing one
to easily grab the whole list or just the "latest/current" one.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200502012248

In response to

pgsql-hackers by date

Next:From: Robin ChauhanDate: 2005-02-02 04:56:14
Subject: Crash when inserting gist records, or creating index on ( int, geom )
Previous:From: Mike RylanderDate: 2005-02-02 02:11:08
Subject: Re: FunctionCallN improvement.

pgsql-patches by date

Next:From: Mark KirkwoodDate: 2005-02-02 04:33:56
Subject: [Fwd: Re: [DOCS] Instructions for FreeBSD ipc config showing age]
Previous:From: Neil ConwayDate: 2005-02-02 01:12:41
Subject: Re: patch for temporary view from TODO list

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