From: Laszlo Nagy <gandalf@shopzeus.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-admin@postgresql.org
Subject: Re: rebellious pg stats collector (reopened case)
Date: Thu, 08 Jan 2009 06:50:25 +0100
Message-ID: <49659421.6060000@shopzeus.com> (raw)
In-Reply-To: <495A1F4D.6050205@shopzeus.com>
References: <49479876.8040607@shopzeus.com>
<20081216134542.GH4741@alvh.no-ip.org>
<494B614C.5060808@shopzeus.com>
<20081219130446.GC4278@alvh.no-ip.org>
<494F67D2.3090406@shopzeus.com>
<6938.1229952228@sss.pgh.pa.us>
<20081222132721.GC10220@alvh.no-ip.org>
<7117.1229952970@sss.pgh.pa.us>
<4958851B.8060500@shopzeus.com>
<7721.1230564393@sss.pgh.pa.us>
<495A1F4D.6050205@shopzeus.com>
Laszlo Nagy írta:
>
>> alive". Otherwise you'll have trouble with the collector not stopping
>> when you want it to. Look into src/backend/storage/ipc/pmsignal.c:
>>
>> - return (getppid() == PostmasterPid);
>> + return (getppid() != 1);
>>
>> (Obviously this is a hack, but it should work on any Unixish system)
>>
Sorry for coming back so late. I changed this, and reinstalled
postgresql but it won't start. Some messages from the log:
Jan 8 00:40:29 shopzeus postgres[80522]: [3814-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:30 shopzeus postgres[80559]: [3849-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:30 shopzeus postgres[80632]: [3917-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:31 shopzeus postgres[80662]: [3946-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:31 shopzeus postgres[80700]: [3981-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:31 shopzeus postgres[80734]: [4014-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:31 shopzeus postgres[80738]: [4017-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:32 shopzeus postgres[80768]: [4046-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:32 shopzeus postgres[80802]: [4078-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:32 shopzeus postgres[80806]: [4079-1] WARNING: terminating
connection because of crash of another server process
Jan 8 00:40:32 shopzeus postgres[80806]: [4079-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
Jan 8 00:40:32 shopzeus postgres[80806]: [4079-3] process exited
abnormally and possibly corrupted shared memory.
Jan 8 00:40:32 shopzeus postgres[80806]: [4079-4] HINT: In a moment
you should be able to reconnect to the database and repeat your command.
Jan 8 00:40:32 shopzeus postgres[80835]: [4109-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:32 shopzeus postgres[80837]: [4110-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:33 shopzeus postgres[80870]: [4141-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:33 shopzeus postgres[80900]: [4170-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:34 shopzeus postgres[80938]: [4205-1] FATAL: the database
system is in recovery mode
Jan 8 00:40:34 shopzeus postgres[80967]: [4233-1] FATAL: the database
system is in recovery mode
(I had to reinstall the original version because it will be used today.)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gandalf@shopzeus.com, tgl@sss.pgh.pa.us
Subject: Re: rebellious pg stats collector (reopened case)
In-Reply-To: <49659421.6060000@shopzeus.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox