| From: | cg(at)osss(dot)net |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #11638: Transaction safety fails when constraints are dropped and analyze is done |
| Date: | 2014-10-10 18:14:33 |
| Message-ID: | 20141010181433.25463.5856@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 11638
Logged by: Casey Allen Shobe
Email address: cg(at)osss(dot)net
PostgreSQL version: 9.3.5
Operating system: Linux (RHEL 5)
Description:
Discovered on 8.4.5, reproducible on 9.3.5.
The paste pretty much explains it all:
http://pgsql.privatepaste.com/162682d176
When, within a transaction:
* I drop a foreign key (or any) constraint.
* Load some data to the table which won't fit the constraint.
* Analyze the table.
* Attempt to re-add the constraint which fails and should roll back the
whole transaction.
The constraint is still missing after rollback.
If I take out the analyze step, it works as expected.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alon | 2014-10-10 18:32:48 | Re: Re: [BUGS] Re: [BUGS] Re: BUG #11431: Failing to backup and restore a Windows postgres database, with Norwegian Bokmål locale. |
| Previous Message | Tom Lane | 2014-10-10 17:58:36 | Re: BUG #11637: SQL function volatility is ignored on index creation |