When one statement has an error then you should see soemthing like the
following returned for the rest:
NOTICE: current transaction is aborted, queries ignored until end of
Meaning none of the rest of the queries are executed.
> -----Original Message-----
> From: John Taylor [mailto:postgres(at)jtresponse(dot)co(dot)uk]
> I'm running a transaction with about 1600 INSERTs.
> Each INSERT involves a subselect.
> I've noticed that if one of the INSERTs fails, the remaining
> INSERTs run in about
> 1/2 the time expected.
> Is postgresql optimising the inserts, knowing that it will
> rollback at the end ?
> If not, why do the queries run faster after the failure ?
pgsql-novice by date
|Next:||From: Tom Lane||Date: 2002-06-12 15:31:49|
|Subject: Re: How efficient are Views |
|Previous:||From: Henshall, Stuart - WCP||Date: 2002-06-12 15:21:15|
|Subject: Re: How efficient are Views|