From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Steve Kehlet <steve(dot)kehlet(at)gmail(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
Date: | 2015-06-16 17:47:50 |
Message-ID: | 20150616174750.GR133018@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera wrote:
> I see another hole in this area. See do_start_worker() -- there we only
> consider the offsets limit to determine a database to be in
> almost-wrapped-around state (causing emergency attention). If the
> database in members trouble has no pgstat entry, it might get completely
> ignored.
For the record -- it was pointed out to me that this was actually fixed
by 53bb309d2. \o/
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2015-06-16 18:35:56 | Re: [GENERAL] pg_xlog on a hot_standby slave filling up |
Previous Message | Melvin Davidson | 2015-06-16 16:05:09 | Re: pg_upgrade problem |
From | Date | Subject | |
---|---|---|---|
Next Message | David Christensen | 2015-06-16 18:25:18 | Re: [PATCH] two-arg current_setting() with fallback |
Previous Message | kjsteuer | 2015-06-16 14:47:04 | Re: Function to get size of notification queue? |