Ryan Kirkpatrick <[EMAIL PROTECTED]> writes:
> #2 0x20dc71 in abort () from /lib/libc.so.6
> #3 0x8080495 in XLogFileOpen ()
Hm. Evidently it's failing to open the xlog file, but the code is set
up in such a way that it dies before telling you why :-( Take a look
at XLogFileOpen in src/backend/access/transam/xlog.c and tweak the code
to tell you the path and errno it's failing on before it abort()s.
regards, tom lane
- [HACKERS] Recovery of PGSQL after system crash failing!!! Ryan Kirkpatrick
- Re: [HACKERS] Recovery of PGSQL after system crash f... Tom Lane
- Re: [HACKERS] Recovery of PGSQL after system crash f... Vadim Mikheev
- Re: [HACKERS] Recovery of PGSQL after system cra... Ryan Kirkpatrick
- Re: [HACKERS] Recovery of PGSQL after system... Ryan Kirkpatrick
- Re: [HACKERS] Recovery of PGSQL after system... Tom Lane
- Re: [HACKERS] Recovery of PGSQL after sy... Vadim Mikheev
- Re: [HACKERS] Recovery of PGSQL aft... Ryan Kirkpatrick
- RE: [HACKERS] Recovery of PGSQL after system crash f... Mikheev, Vadim
- RE: [HACKERS] Recovery of PGSQL after system cra... Ryan Kirkpatrick
- [HACKERS] Re: Recovery of PGSQL after system... Thomas Lockhart
- Re: [HACKERS] Re: Recovery of PGSQL afte... Bruce Momjian
- Re: [HACKERS] Re: Recovery of PGSQL afte... Tom Lane
- Re: [HACKERS] Re: Recovery of PGSQL... Peter Eisentraut
- Re: [HACKERS] Re: Recovery of P... Bruce Momjian
- Re: [HACKERS] Re: Recovery of P... Ryan Kirkpatrick
