Skip site navigation (1) Skip section navigation (2)

Re: 7.5dev assertion failure w/ v3 protocol and transactions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 7.5dev assertion failure w/ v3 protocol and transactions
Date: 2004-07-29 21:57:03
Message-ID: 17310.1091138223@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Kris Jurka <books(at)ejurka(dot)com> writes:
> This also produces a second core file in the directory the postmaster was 
> started in which contains:

> #0  0x402a5721 in kill () from /lib/libc.so.6
> #1  0x402a54c5 in raise () from /lib/libc.so.6
> #2  0x402a69e8 in abort () from /lib/libc.so.6
> #3  0x08231994 in errfinish (dummy=0) at elog.c:473
> #4  0x080b1e2c in ReadControlFile () at xlog.c:3130
> #5  0x080b2257 in XLOGShmemInit () at xlog.c:3381

This appears to be here:

        ereport(PANIC,
                (errcode_for_file_access(),
                 errmsg("could not open control file \"%s\": %m",
                        ControlFilePath)));

but it's difficult to go any further without knowing the errno.
I certainly can't think of any good reason why the recovery process
should be unable to open pg_control.  Do you have the postmaster log?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Kris JurkaDate: 2004-07-29 22:05:53
Subject: Re: 7.5dev assertion failure w/ v3 protocol and transactions
Previous:From: Kris JurkaDate: 2004-07-29 21:05:00
Subject: Re: 7.5dev assertion failure w/ v3 protocol and transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group