Re: Separating bgwriter and checkpointer - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Separating bgwriter and checkpointer
Date
Msg-id CA+U5nM+xV9P5fEv2OB3oyYs1-fPh-NVNUAAO1rmmeSgomyuKfg@mail.gmail.com
Whole thread Raw
In response to Re: Separating bgwriter and checkpointer  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Separating bgwriter and checkpointer
List pgsql-hackers
On Tue, Oct 4, 2011 at 10:05 AM, Simon Riggs <simon@2ndquadrant.com> wrote:

>> ============== shutting down postmaster               ==============
>> pg_ctl: server does not shut down
>> pg_regress: could not stop postmaster: exit code was 256
>>
>
> Yes, I see this also. At the same time, pg_ctl start and stop seem to
> work fine in every mode, which is what I tested. Which seems a little
> weird.
>
> I seem to be having problems with HEAD as well.
>
> Investigating further.


Doh.

The problem is the *same* one I fixed in v2, yet now I see I managed
to somehow exclude that fix from the earlier patch. Slap. Anyway,
fixed again now.

Problem observed in head was because of this bug causing later make
checks to fail on port 57432, so it looked like a problem in head at
first. Nothing actual bug there at all.

Thanks for your patience.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: "Mr. Aaron W. Swenson"
Date:
Subject: Re: Bug with pg_ctl -w/wait and config-only directories
Next
From: "Mr. Aaron W. Swenson"
Date:
Subject: Re: Bug with pg_ctl -w/wait and config-only directories