Re: BUG #4121: ERROR: could not open relation 1663/16403/469917: Invalid argument

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Boldinov <bldnv(at)mail(dot)ru>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4121: ERROR: could not open relation 1663/16403/469917: Invalid argument
Date: 2008-04-22 07:57:09
Message-ID: 480D9A55.8060009@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Try to look into base/16403/ directory and check if file 469917 exists. And run

select relname from pg_class where relfilenode=469917

to determine which relation (table) is affected.

Zdenek

PS: 8.1 version of PostgreSQL is not supported on win. Use 8.3

Boldinov napsal(a):
> The following bug has been logged online:
>
> Bug reference: 4121
> Logged by: Boldinov
> Email address: bldnv(at)mail(dot)ru
> PostgreSQL version: 8.1.5
> Operating system: Windows Server 2003 Standart
> Description: ERROR: could not open relation 1663/16403/469917:
> Invalid argument
> Details:
>
> 2008-04-21 14:35:41 ERROR: could not open relation 1663/16403/469917:
> Invalid argument
> 2008-04-21 14:35:41 STATEMENT: SELECT
> _Reference130._IDRRef AS f_3,
> _Reference130._Description AS f_4
> FROM
> _Reference130
> WHERE
> _Reference130._IDRRef =
> '\\200"\\000\\033x0\\004\\032\\021\\334\\250\\246\\360\\024\\017_'::bytea
> AND (FALSE = TRUE OR
> EXISTS(
> SELECT
> 0 AS f_2
> FROM
> (
> SELECT
> TRUE AS _f_1
> ) _V8TblAli1
> INNER JOIN _InfoReg16060 _InfoReg16060_Q_000_T_002
> ON _InfoReg16060_Q_000_T_002._Fld16061_TYPE = '\\010'::bytea AND
> _InfoReg16060_Q_000_T_002._Fld16061_RTRef = '\\000\\000\\000\\236'::bytea
> AND _InfoReg16060_Q_000_T_002._Fld16061_RRRef = _Reference130._OwnerIDRRef
> AND _InfoReg16060_Q_000_T_002._Fld16062RRef =
> '\\205Y\\011U\\377\\362\\015\\220D''_3\\367\\352\\200\\247'::bytea AND
> _InfoReg16060_Q_000_T_002._Fld16063_TYPE = '\\010'::bytea AND
> (_InfoReg16060_Q_000_T_002._Fld16063_RTRef ||
> _InfoReg16060_Q_000_T_002._Fld16063_RRRef) IN ('\\000\\000\\0002'::bytea ||
> '\\200"\\000\\033x0\\004\\032\\021\\334\\262\\273<\\265)4'::bytea,'\\000\\00
> 0\\0002'::bytea ||
> '\\245\\230\\272~\\361\\313\\223fG\\034\\011\\207X\\325q\\016'::bytea,'\\000
> \\000\\000\\324'::bytea ||
> '\\257\\332\\000\\004#R\\244\\374\\021\\334\\206\\326\\355\\252j\\360'::byte
> a) AND _InfoReg16060_Q_000_T_002._Fld16065 = TRUE))
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2008-04-22 08:04:42 Re: ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target
Previous Message John Parnefjord 2008-04-22 06:53:07 ERROR: failed to re-find parent key in "sl_seqlog_idx" for deletion target