Re: Obscure problem due to high system OID or privileges?

Hello,

-------- Original-Nachricht --------
> Datum: Mon, 03 Jan 2011 11:05:30 -0500
> Von: Tom Lane <tgl@sss.pgh.pa.us>
> An: "Jan-Peter Seifert" <Jan-Peter.Seifert@gmx.de>
> CC: pgsql-admin@postgresql.org
> Betreff: Re: [ADMIN] Obscure problem due to high system OID or privileges?

> "Jan-Peter Seifert" <Jan-Peter.Seifert@gmx.de> writes:
> > During 'start up' the application does a couple of SELECTs on
> pg_catalog:
>
> > SELECT COUNT(*) FROM pg_attribute JOIN pg_type ON
> pg_attribute.atttypid=pg_type.oid LEFT OUTER JOIN pg_attrdef ON (
> pg_attribute.attnum=pg_attrdef.adnum   AND pg_attribute.attrelid=pg_attrdef.adrelid ) WHERE
> pg_attribute.attrelid = 2147483647 AND pg_attribute.attnum >= 0 AND
> pg_attribute.attisdropped = 'false'
>
> Is the table it's looking for really exactly OID 2147483647 (ie 2^31-1)?
> That seems a bit improbable.  I suspect something in your app is choking
> on an OID that is in fact larger than that, and it's somehow getting
> clamped to INT_MAX.

Err - that's really very suspicious as it's a 32-Bit application. We'll test it again with a clone of the server
instanceas I'm not sure whether it was a log from a try on the current database restore. Could take some time though. 

Thank you very much!

Peter
--
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
gratis Handy-Flat! http://portal.gmx.net/de/go/dsl