On 28.12.2012 20:55, Phil Sorber wrote:
Postgres 9.0.11 running as a hot standby.
The master was restarted and the standby went into a segmentation
fault loop. A hard stop/start fixed it. Here are pertinent logs with
excess and identifying information removed:
...
If there is any more info I can provide, let me know. This is a
production DB so I won't be able to do any disruptive testing. Based
on what I have seen so far, I think this would be difficult to
replicate anyway.
A stack trace would be nice. If you didn't get a core dump this time, it
would be good to configure the system so that you get one next time it
happens.
- Heikki
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
