From: | Robert Treat <robert(at)omniti(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, jesus(at)omniti(dot)com |
Subject: | Re: 8.5alpha3 hot standby crash report (DatabasePath related?) |
Date: | 2010-01-07 21:56:44 |
Message-ID: | 9E00B4CD-041C-4D11-9A9F-5ABC5AE56749@omniti.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan 7, 2010, at 4:15 PM, Simon Riggs wrote:
> On Thu, 2010-01-07 at 14:41 -0500, Robert Treat wrote:
>
>> Doing some testing with 8.5alpha3, my standby crashed this morning
>> whilst
>> doing some testing. Seems I have a core file, so thought I would
>> send a report.
>>
>> Version: PostgreSQL 8.5alpha3 on i386-pc-solaris2.10, compiled by
>> GCC gcc
>> (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath), 32-bit
>>
>> Error in the log was simply this:
>> LOG: restored log file "000000010000000300000032" from archive
>> LOG: startup process (PID 385) was terminated by signal 11
>> LOG: terminating any other active server processes
>
> Please send some more of the prior log, so we can tell the
> initialization state at that point.
>
Not much more to send really. It's just "restored log file" lines
going back to the startup (as expected)
> If you can reproduce it, that would help also. Thanks.
>
Not sure about reproducing, but if I restart the database, it crashes
again during log replay (stack trace info looks the same).
LOG: database system was interrupted while in recovery at log time
2010-01-07 12:01:57 EST
HINT: If this has occurred more than once some data might be
corrupted and you might need to choose an earlier recovery target.
LOG: starting archive recovery
LOG: restore_command = '/export/home/postgres/pgwork/inst/slave/bin/
pg_standby /export/home/postgres/pgwork/data/.hot_standby %f %p %r'
cp: cannot access /export/home/postgres/pgwork/data/.hot_standby/
00000001.history
cp: cannot access /export/home/postgres/pgwork/data/.hot_standby/
00000001.history
cp: cannot access /export/home/postgres/pgwork/data/.hot_standby/
00000001.history
cp: cannot access /export/home/postgres/pgwork/data/.hot_standby/
00000001.history
LOG: restored log file "00000001000000030000002A" from archive
LOG: automatic recovery in progress
LOG: initializing recovery connections
LOG: redo starts at 3/2A000020, consistency will be reached at
3/2D000120
LOG: restored log file "00000001000000030000002B" from archive
LOG: restored log file "00000001000000030000002C" from archive
LOG: restored log file "00000001000000030000002D" from archive
LOG: consistent recovery state reached at 3/2D000120
LOG: database system is ready to accept read only connections
LOG: restored log file "00000001000000030000002E" from archive
LOG: restored log file "00000001000000030000002F" from archive
LOG: restored log file "000000010000000300000030" from archive
LOG: restored log file "000000010000000300000031" from archive
LOG: restored log file "000000010000000300000032" from archive
LOG: startup process (PID 4397) was terminated by signal 11
LOG: terminating any other active server processes
--
Robert Treat
http://www.omniti.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2010-01-07 21:59:13 | Re: RFC: PostgreSQL Add-On Network |
Previous Message | Andres Freund | 2010-01-07 21:37:56 | Re: Hot Standy introduced problem with query cancel behavior |