| From: | "Dmitry Belyavsky" <beldmit(at)masterhost(dot)ru> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #3233: Trigger checks failed on concurrent transactions |
| Date: | 2007-04-17 10:32:50 |
| Message-ID: | 200704171032.l3HAWo6r047277@wwwmaster.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 3233
Logged by: Dmitry Belyavsky
Email address: beldmit(at)masterhost(dot)ru
PostgreSQL version: 8.1.6
Operating system: FreeBSD 6
Description: Trigger checks failed on concurrent transactions
Details:
Greetings!
I have a table containing IP ranges and a BEFORE INSERT trigger checking the
ranges I insert don't intersect already existing ranges. So the concurrent
transactions are able to insert 2 intersecting ranges.
Whether TODO record "Allow statement-level triggers to access modified rows"
concerns the case I report?
Is there any workaround except LOCK TABLE causing performance degradation?
Thank you!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-04-17 12:51:15 | Re: Grantor name gets lost when grantor role dropped |
| Previous Message | Russell Smith | 2007-04-17 08:02:51 | Re: Grantor name gets lost when grantor role dropped |