Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Mark Llewellyn <mark_llewellyn(at)adp(dot)com>, pgsql-hackers(at)postgresql(dot)org, Sujeet Rajguru <sujeet(dot)rajguru(at)enterprisedb(dot)com>
Subject: Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Date: 2010-11-27 00:16:20
Message-ID: AANLkTinfpBj9SJzvZJ9Q8YrZ-f6nDfzmaTScMZCLXNeP@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Fri, Nov 26, 2010 at 6:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Speaking of classifying errors, should we have a fourth result value to
> cover "obviously bogus parameters"?

+1.

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2010-11-27 00:45:56 Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Previous Message Craig Ringer 2010-11-26 23:56:50 Re: BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-11-27 00:18:04 Re: duplicate connection failure messages
Previous Message Robert Haas 2010-11-27 00:11:09 Re: [GENERAL] column-level update privs + lock table