Re: BUG #5118: start-status-insert-fatal - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #5118: start-status-insert-fatal
Date
Msg-id 4B8277D3020000250002F493@gw.wicourts.gov
Whole thread Raw
In response to Re: BUG #5118: start-status-insert-fatal  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
Bruce Momjian <bruce@momjian.us> wrote:

> I think you should just edit the TODO wiki and list all the things
> we agree need fixing

Will do.  It may take me a while to chase down all the issues from
the LSB script work.

If I recall correctly, some of what I was looking at seems necessary
for a well-behaved LSB conforming script, and there was support for
the ideas from some quarters, but it fell short of what I'd consider
a consensus (for example, escalating the stop request level over
time).  Do we want to get into a discussion of such issues at this
point, add them to the list with a note that discussion is needed
before undertaking them, or should I keep them just in my own list?

A couple comments which I think were the last on the escalation of
stop mode:

http://archives.postgresql.org/pgsql-hackers/2009-09/msg01145.php

http://archives.postgresql.org/pgsql-hackers/2009-09/msg01158.php

Before continuing that discussion, I think we need to decide if *now
is the time* to continue that discussion (and other related ones);
and I would argue such discussion should wait. These links are just
provided to help answer the question of what I should do with such
disputed issues when I update the TODO list.  I don't want to slip
something in without consensus, but I don't want the issue to be
lost, or missed by anyone who takes on pg_ctl work.

-Kevin

pgsql-bugs by date:

Previous
From: "Jonathan "Duke" Leto"
Date:
Subject: BUG #5339: Version of Perl detected incorrectly
Next
From: Alex Hunsaker
Date:
Subject: Re: BUG #5339: Version of Perl detected incorrectly