| From: | pgsql-bugs(at)postgresql(dot)org |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | duplicated rows on update when client dies |
| Date: | 2000-08-25 19:28:54 |
| Message-ID: | 200008251928.e7PJSs345566@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Richard Gonda (zigur(at)matavnet(dot)hu) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
duplicated rows on update when client dies
Long Description
We expected if a network client dies in update proceess (in case example power off), duplicated rows remained in database, the old and updated rows too. it will be work, but on vacuum it cause bug on uniquie keys. Another strange expecting after crash : deleting. for example DELETE FROM table WHERE prim_code > 10 -> 80 DELETED. Again this delete command, 120 DELETED.. and again. We expected only on network client this, never on locally connnected client.
Sample Code
No file was uploaded with this report
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql-bugs | 2000-08-25 19:47:16 | Any user able to connect to a database can create tables/etc |
| Previous Message | pgsql-bugs | 2000-08-25 13:48:53 | wrong permissions for triggers invoked by rewrite rules |