Re: StandbyAcquireAccessExclusiveLock doesn't necessarily

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: StandbyAcquireAccessExclusiveLock doesn't necessarily
Date: 2018-09-11 16:51:36
Message-ID: 20180911165136.o4fqyjylbk3sbsuk@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-09-11 12:50:06 -0400, Tom Lane wrote:
> I am not sure which part of "I will not fix this" you didn't understand.

Maybe the "this is an open list, and we can discuss things" bit?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2018-09-11 17:03:41 Re: libpq stricter integer parsing
Previous Message Tom Lane 2018-09-11 16:50:06 Re: StandbyAcquireAccessExclusiveLock doesn't necessarily