| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby |
| Date: | 2014-06-27 18:51:42 |
| Message-ID: | 20140627185142.GO7340@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Jeff Janes wrote:
> This problem was initially fairly easy to reproduce, but since I
> started adding instrumentation specifically to catch it, it has become
> devilishly hard to reproduce.
>
> I think my next step will be to also log each of the values which goes
> into the complex if (...) expression that decides on the deletion.
Could you please to reproduce it after updating to latest? I pushed
fixes that should close these issues. Maybe you want to remove the
instrumentation you added, to make failures more likely.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | BM-2cUR7NEMQCynXF7KDxiMP1J9CMpmKA5Bd5 | 2014-06-27 19:26:03 | Re: BUG #10785: error if using x>n AND x<m in where clause, BETWEEN n AND m works as supposed |
| Previous Message | Tom Lane | 2014-06-27 18:19:46 | Re: BUG #10785: error if using x>n AND x<m in where clause, BETWEEN n AND m works as supposed |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2014-06-27 18:56:28 | Re: Atomics hardware support table & supported architectures |
| Previous Message | Tom Lane | 2014-06-27 18:26:06 | Re: Atomics hardware support table & supported architectures |