Re: Hot standby stops after a few days of inactivity (i.e. no new WAL) - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Hot standby stops after a few days of inactivity (i.e. no new WAL)
Date
Msg-id 20081104133752.GC3958@alvh.no-ip.org
Whole thread Raw
In response to Hot standby stops after a few days of inactivity (i.e. no new WAL)  (Marc Schablewski <ms@clickware.de>)
Responses Re: Hot standby stops after a few days of inactivity (i.e. no new WAL)
List pgsql-general
Marc Schablewski wrote:
> Hi,
>
> we are running a PostgreSQL 8.3.3 on a Linux box (SuSE 10.3, 2.6.22
> kernel) as a hot standby. After some maintenances work the WAL files
> couldn't be shipped to that system (which had nothing to do with
> postgres, as we found out later). The problem was not noticed for about
> a week. When looking for a reason why the WAL weren't shipped, we found
> the following error message:
>
> 2008-10-31 17:07:52 CET 9162LOG:  received smart shutdown request
> 2008-10-31 17:07:52 CET 9178FATAL:  could not restore file
> "000000010000008600000018" from archive: return code 15

This server was stopped intentionally by someone or something, external
to Postgres itself.  "Smart shutdown" means the postmaster got SIGTERM.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-general by date:

Previous
From: "Sathish Duraiswamy"
Date:
Subject: Re: epqa; postgres performance optimizer support tool; opensource.
Next
From: Laczi József
Date:
Subject: don't use GIN index, when i use =any