| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Condition variable live lock |
| Date: | 2018-01-09 04:02:32 |
| Message-ID: | CA+TgmoZTJw_N8+cuJBAz_jKs=-T8PCBH2nVCq80eQ7LBEMx_zw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 8, 2018 at 7:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm not real sure BTW why we have some callers that ereport and some
> that just exit(1). Seems like it would be better to be consistent,
> though I'm not entirely sure which behavior to standardize on.
I think at one point we had an idea that regular backends would FATAL
if the postmaster fell over and other processes (e.g. checkpointer,
bgwriter) would exit silently. Whether that was the right idea, and
whether it's still is/was ever what the code did, I'm not sure.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2018-01-09 04:05:30 | Re: Parallel append plan instability/randomness |
| Previous Message | Bruce Momjian | 2018-01-09 03:48:10 | Re: Invalid pg_upgrade error message during live check |