[Moving back on-list. Tom generously offered to look at the server in
question, since it seemed likely that a testcase would be difficult or
impossible to reproduce in this case]
On Fri, Dec 2, 2011 at 12:07 AM, Tom Lane wrote:
>
> Well, poking around in the process at the moment of SIGBUS, I fin
Josh Kupershmidt writes:
> Here's a backtrace from 9.1 tip with CFLAGS="-O0", server logs are as before:
> Program received signal SIGBUS, Bus error.
> 0x00c9716b in ?? () from /lib/i386-linux-gnu/libc.so.6
> (gdb) bt
> #0 0x00c9716b in ?? () from /lib/i386-linux-gnu/libc.so.6
> #1 0x082b3b2f i
On Wed, Nov 30, 2011 at 10:50 PM, Tom Lane wrote:
> Josh Kupershmidt writes:
>> On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane wrote:
> It might be worth recompiling at -O0, first to see if that changes the
> behavior and second to see if it changes the reported stack trace.
Here's a backtrace from
Josh Kupershmidt writes:
> On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane wrote:
>> Can you try that on 9.1 branch tip to see if it's already fixed?
> Hrm, don't think that helped - I get the same error in the logs using
> a checkout of branch REL9_1_STABLE.
Well, was worth a try, although the stack
On Wed, Nov 30, 2011 at 9:17 PM, Tom Lane wrote:
> Can you try that on 9.1 branch tip to see if it's already fixed?
Hrm, don't think that helped - I get the same error in the logs using
a checkout of branch REL9_1_STABLE.
Josh
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
Josh Kupershmidt writes:
> I have a new 9.1.1 hot standby machine (VM). It consistently starts
> up, goes through recovery through these same WAL segments, and then
> gets a "Bus error":
Can you try that on 9.1 branch tip to see if it's already fixed?
regards, tom lane
-
Hi all,
I have a new 9.1.1 hot standby machine (VM). It consistently starts
up, goes through recovery through these same WAL segments, and then
gets a "Bus error":
2011-11-30 20:57:37 EST LOG: database system was interrupted while in
recovery at log time 2011-11-30 09:37:11 EST
2011-11-30 20:57:
