Re: Continue transactions after errors in psql - Mailing list pgsql-patches

From Greg Sabino Mullane
Subject Re: Continue transactions after errors in psql
Date
Msg-id 8553602d0cbdcbb254f5161277bad4f6@biglumber.com
Whole thread Raw
In response to Re: Continue transactions after errors in psql  ("Michael Paesold" <mpaesold@gmx.at>)
List pgsql-patches
-----BEGIN PGP SIGNED MESSAGE-----
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@turnstep.com
PGP Key: 0x14964AC8 200502012248
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFCAE5IvJuQZxSWSsgRAqy7AJ4wo03ir/qRlRUxdC4sXId4OvlsswCgy50l
ldB3hFJaO88sBV1rfbADwwU=
=la3h
-----END PGP SIGNATURE-----



pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: patch for temporary view from TODO list
Next
From: Tom Lane
Date:
Subject: Re: patch for temporary view from TODO list