What version of PG are you using? (just wondering so I can know if this
another 8.3 or something newer)
Are you using cursors ? (again just wondering)
I still haven't been able to reproduce in our dev machines only seeing this
issue in our production servers. (that handle several orders of magnitude
more traffic and data then I can generate in our dev servers)
Right now I am working on getting a patch to our functions at various db
servers that drops tables to first get an LOCK TABLE <parent table> IN
ACCESS EXCLUSIVE MODE before dropping child tables.
It's kind of a heavy hammer to have to use on a high transaction
environment, but I am hoping this will eliminate the problem in our
environment.
I probably won't know for a month if this will fix the issue or not, as that
is the pace that we move at. If try it I would like to hear back.
- Mark
-----Original Message-----
From: pgsql-novice-owner@postgresql.org
[mailto:pgsql-novice-owner@postgresql.org] On Behalf Of bakkiya
Sent: Friday, November 19, 2010 7:17 AM
To: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] Could not open relation with OID (table partitioning
issue?)
Hi.
We are also facing similar problem with postgresql partition tables. We are
querying 2 days old partition table and at the same time we are dropping 2
months old partition.Sometimes our queries are getting failed with "ERROR:
could not open relation with OID 1761740". We have set the constraint
exclusion to on. Can you please help us on resolving it?
Regards,
Bakki
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Could-not-open-relation-with-OID-tab
le-partitioning-issue-tp3265708p3272358.html
Sent from the PostgreSQL - novice mailing list archive at Nabble.com.
--
Sent via pgsql-novice mailing list (pgsql-novice@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-novice
