| From: | "Jan Peters" <petersjan(at)gmx(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Rollback locks table - why? |
| Date: | 2008-03-20 15:17:58 |
| Message-ID: | 20080320151758.188000@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Hello Tom,
> so the problem must be in something you didn't show us. What exactly
> are you doing to decide that you need to roll back? Also, none of these
> statements (except the CREATE) would take an exclusive lock on test, so
> there must be something else going on that you didn't show us.
That is exactly what confuses me. I just put the above code in the SQL Query Editor of my Admin App (e.g. PGAdmin III) and click the run button, nothing else. First time I get "duplicate unique key" second time "
ERROR: current transaction is aborted, commands ignored until end of transaction block"...
Regards
Jan
--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/?mc=sv_ext_mf(at)gmx
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Peters | 2008-03-20 15:20:34 | Re: Rollback locks table - why? |
| Previous Message | Tom Lane | 2008-03-20 15:11:34 | Re: Rollback locks table - why? |