| From: | "" <postgresql_atomicity(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #2647: Atomicity issues when using rules |
| Date: | 2006-09-23 17:43:36 |
| Message-ID: | 200609231743.k8NHhaDF008345@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: 2647
Logged by:
Email address: postgresql_atomicity(at)yahoo(dot)com
PostgreSQL version: 8.1
Operating system: Debian GNU/Linux
Description: Atomicity issues when using rules
Details:
When I ensure atomicity by locking tables in a transaction, my transactions
still break when I have additional tables touched by rules on tables I
explicitly locked. I can work around by also locking them, but this breaks
modularity of the rules. There should be the policy, or at least the option
when creating the rule of also locking the referenced tables of the rules
automatically when locking the table on which the rule was defined.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-23 17:44:29 | Re: Corruption of multibyte identifiers on UTF-8 locale |
| Previous Message | Victor Snezhko | 2006-09-23 17:33:47 | Re: Corruption of multibyte identifiers on UTF-8 locale |