Re: RFC: Add 'taint' field to pg_control.

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,Craig Ringer <craig(at)2ndquadrant(dot)com>,Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RFC: Add 'taint' field to pg_control.
Date: 2018-03-08 02:18:28
Message-ID: B6305103-A75E-4BE4-A5C9-83B623CA3EED@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On March 7, 2018 5:51:29 PM PST, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>My favourite remains an organisation that kept "fixing" an issue by
>kill
>-9'ing the postmaster and removing postmaster.pid to make it start up
>again. Without killing all the leftover backends. Of course, the system
>kept getting more unstable and broken, so they did it more and more
>often.
>They were working on scripting it when they gave up and asked for help.

Maybe I'm missing something, but that ought to not work. The shmem segment that we keep around would be a conflict, no?

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-03-08 02:26:20 Re: Some message fixes
Previous Message Alvaro Herrera 2018-03-08 01:57:08 Re: FOR EACH ROW triggers on partitioned tables