| From: | daniele(dot)varrazzo(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #7572: virtualxid lock held by bgwriter on promoted slaves |
| Date: | 2012-09-26 21:33:26 |
| Message-ID: | E1TGzEU-0005zV-JC@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: 7572
Logged by: Daniele Varrazzo
Email address: daniele(dot)varrazzo(at)gmail(dot)com
PostgreSQL version: 9.1.4
Operating system: Linux
Description:
Hello,
when a slave is promoted, the pgwriter keeps holding a lock with virtualxid
"1/1" and virtualtransaction "-1/0". Such lock stops pg_reorg to run (as
reported here:
http://pgfoundry.org/tracker/index.php?func=detail&aid=1011203&group_id=1000411&atid=1376)
but I've verified the same condition on 9.1.4).
Is it possible to free that lock on slave promotion?
Is it safe to ignore that lock for pg_reorg sake? The program is which is
probably waiting for all the transactions to finish before swapping the
table in the system catalog but I'm not sure about that yet.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-26 23:13:39 | Re: BUG #7570: WHERE .. IN bug from 9.2.0 not fixed in 9.2.1 |
| Previous Message | radovan.jablonovsky | 2012-09-26 21:24:54 | BUG #7571: Query high memory usage |