Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Re: strange commit behavior - Mailing list pgsql-general

From Grzegorz Jaśkiewicz
Subject Re: strange commit behavior
Date
Msg-id 2f4958ff0811180537r53c3b9bdga5fa581a8a10b8a@mail.gmail.com
Whole thread Raw
In response to Re: strange commit behavior  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general


On Tue, Nov 18, 2008 at 1:25 PM, Craig Ringer <craig@postnewspapers.com.au> wrote:


You can use savepoints (see the manual) to recover from errors, though
they have some issues if you use hundreds of thousands of savepoints in
a single transaction. It's much better to check the data on INSERT to
make sure it's OK. You can do this with an INSERT ... SELECT (and check
the rowcount), with a PL/PgSQL function that returns a result value, do
it client-side, etc.

can you post an example ?
would that also resolve problem with 'rowcount' left unset, if trigger or rule is used on table ?
 

--
GJ

pgsql-general by date:

Previous
From: "A. Kretschmer"
Date:
Subject: Re: Urgent - Grant
Next
From: Gustavo Rosso
Date:
Subject: Re: Urgent - Grant