Re: Warm standby stall -- what debug info would help?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-hackers(at)postgresql(dot)org>, "Kevin Grittner" <Kgrittn(dot)CCAP(dot)Courts(at)wicourts(dot)gov>
Subject: Re: Warm standby stall -- what debug info would help?
Date: 2007-07-09 16:37:11
Message-ID: 46921DE7.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> On Mon, Jul 9, 2007 at 10:54 AM, in message
<469213FB(dot)EE98(dot)0025(dot)0(at)wicourts(dot)gov>, "Kevin Grittner"
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> We're running a number of warm standby instances on one server. One of them
> stalled on Saturday. When I found that this morning, I confirmed that the
> files were in the directory from which it should be pulling the WAL files.
> The logs showed normal processing up to the stall, with no messages
> afterwards. I tried a restart and it resumed warm standby status and caught
> up quickly.

No, actually it stalled on the same WAL file. I've got another one in the
same state that I haven't touched yet. I'll work on gathering what info I
can think of, but if there's something in particular you would like to see,
let me know.

More in a bit.

Should this be on the bugs list instead of hackers?

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-07-09 16:57:52 psql/pg_dump vs. dollar signs in identifiers
Previous Message Tom Lane 2007-07-09 16:36:56 Re: Warm standby stall -- what debug info would help?