Postgres Pro
Downloads
Home   >   mailing lists

Re: StandbyAcquireAccessExclusiveLock doesn't necessarily - Mailing list pgsql-hackers

From Robert Haas
Subject Re: StandbyAcquireAccessExclusiveLock doesn't necessarily
Date
Msg-id CA+TgmoasJ8xBt2F2QXRaf1q8+9auXFi2QT_fWMrWpCX837mkxw@mail.gmail.com
Whole thread Raw
In response to StandbyAcquireAccessExclusiveLock doesn't necessarily  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: StandbyAcquireAccessExclusiveLock doesn't necessarily  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Fri, Sep 7, 2018 at 6:37 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So my inclination is to remove the reportMemoryError = false parameter,
> and just let an error happen in the unlikely situation that we hit OOM
> for the lock table.

Wouldn't that take down the entire cluster with no restart?

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

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: can commitfest application resend a mail?
Next
From: legrand legrand
Date:
Subject: Re: pg_stat_statements query jumbling question