Re: [bug fix] "pg_ctl stop" times out when it should respond quickly

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: MauMau <maumau307(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [bug fix] "pg_ctl stop" times out when it should respond quickly
Date: 2013-12-24 15:30:47
Message-ID: 52B9A8A7.504@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/5/13, 7:07 AM, MauMau wrote:
> From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>> If you're going to do a postmaster_is_alive check, why bother with
>> repeated get_pgpid()?
>
> As I said yesterday, I removed get_pgpid() calls. I'll add this patch
> to 2014-1 commitfest this weekend if it is not committed until then.

This patch breaks the regression tests:

xml ... ok
test stats ... ok
============== shutting down postmaster ==============
<waits a long time>
pg_ctl: server does not shut down

pg_regress: could not stop postmaster: exit code was 256

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-12-24 15:33:47 Re: GIN improvements part 1: additional information
Previous Message Fabien COELHO 2013-12-24 15:29:03 Re: ISN extension bug? (with patch)