| From: | Zeugswetter Andreas SEV <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Trigger aborted on error |
| Date: | 1999-11-02 09:22:40 |
| Message-ID: | 219F68D65015D011A8E000006F8590C60339E15C@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Have you put an index on the field in question? It shouldn't
> matter how
> many records you have if you do. If you don't, no other database will
> help you any better.
The main problem is, that PostgreSQL will abort the transaction if it raises
elog(ERROR...).
No other DB does this. Thus on other DB's the user program can check the
return code,
fix the error condition and still commit the transaction.
I think behavior like this will be easier to provide with WAL's savepoints.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SEV | 1999-11-02 09:50:22 | AW: [HACKERS] sort on huge table |
| Previous Message | Peter Eisentraut | 1999-11-02 09:20:33 | Re: [GENERAL] users in Postgresql |