Re: StandbyAcquireAccessExclusiveLock doesn't necessarily

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 14:53:02
Message-ID: CA+TgmoaY5KivibJHPWyECMh+4m8Z_1Spj_gqcPVcy4Xz390V0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 11, 2018 at 5:54 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Please explain why you think that would be with no restart.

Because the startup process will die, and if that happens, IIRC,
there's no crash-and-restart loop. You're just done.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2018-09-11 14:57:33 Re: pgbench - add pseudo-random permutation function
Previous Message David Fetter 2018-09-11 14:47:21 Re: CREATE ROUTINE MAPPING