| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(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 09:54:16 |
| Message-ID: | CANP8+jLttaWVs+Dn+inyrqB4attSKaywavFEkOCO5eQN91DT8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10 September 2018 at 19:16, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Sep 7, 2018 at 6:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
>
Please explain why you think that would be with no restart.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksandr Parfenov | 2018-09-11 10:31:50 | Re: Flexible configuration for full-text search |
| Previous Message | Amit Khandekar | 2018-09-11 09:20:41 | Re: Query is over 2x slower with jit=on |