| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jan-Peter Seifert" <Jan-Peter(dot)Seifert(at)gmx(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Obscure problem due to high system OID or privileges? |
| Date: | 2011-01-03 16:05:30 |
| Message-ID: | 20082.1294070730@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Jan-Peter Seifert" <Jan-Peter(dot)Seifert(at)gmx(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan-Peter.Seifert | 2011-01-03 16:29:22 | Re: Obscure problem due to high system OID or privileges? |
| Previous Message | Jan-Peter Seifert | 2011-01-03 14:16:02 | Obscure problem due to high system OID or privileges? |