Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id E6E921337999 for ; Mon, 3 Jan 2011 12:29:34 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 06937-03 for ; Mon, 3 Jan 2011 16:29:27 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mail.postgresql.org (Postfix) with SMTP id 2262813364DE for ; Mon, 3 Jan 2011 12:29:26 -0400 (AST) Received: (qmail 11735 invoked by uid 0); 3 Jan 2011 16:29:25 -0000 Received: from 192.124.237.1 by www050.gmx.net with HTTP; Mon, 03 Jan 2011 17:29:22 +0100 (CET) Cc: pgsql-admin@postgresql.org Content-Type: text/plain; charset="utf-8" Date: Mon, 03 Jan 2011 17:29:22 +0100 From: Jan-Peter.Seifert@gmx.de In-Reply-To: <20082.1294070730@sss.pgh.pa.us> Message-ID: <20110103162922.4730@gmx.net> MIME-Version: 1.0 References: <20110103141602.204670@gmx.net> <20082.1294070730@sss.pgh.pa.us> Subject: Re: Obscure problem due to high system OID or privileges? To: Tom Lane X-Authenticated: #955937 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX18HUPtTKXIH6InioIvSD5Shy1TV2v4bvr4NQol+m3 yX6vQV1+HcrmQlpX561TdM+itCP+gztm5QhQ== Content-Transfer-Encoding: 8bit X-GMX-UID: A5VKJZBUTlI8X0nzeWhrz1FOU2poZdlZ X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201101/6 X-Sequence-Number: 36446 Hello, -------- Original-Nachricht -------- > Datum: Mon, 03 Jan 2011 11:05:30 -0500 > Von: Tom Lane > An: "Jan-Peter Seifert" > CC: pgsql-admin@postgresql.org > Betreff: Re: [ADMIN] Obscure problem due to high system OID or privileges? > "Jan-Peter Seifert" 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 instance as 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