From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Jaiswal Dhaval Sudhirkumar <JaiswalDS(at)microland(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: >>relation with OID 1211822032 does not exist |
Date: | 2010-06-08 13:00:33 |
Message-ID: | 4C0E3EF1.7020903@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/06/2010 8:25 PM, Jaiswal Dhaval Sudhirkumar wrote:
> Hi All,
>
> We are getting following error on intermittent basis when we write data
> into database. We are on postgreSQL 8.0.2
While this doesn't help you track down your problem directly ... 8.0.2?
Really? Version 8.0 is up to patch level 25 (!!) so you're missing out
on a LOT of bug fixes. 8.0 needed plenty of them, too :S
Anyway, first I strongly recommend that you try to pg_dumpall and make
sure you keep that dump somewhere other than the problem machine.
Next, I'd look at whether that report could be coming from a stored
procedure that hadn't been re-loaded after a table/view/proc that it
uses changed. Before 8.3, stored procedures had to be reloaded after
such changes (and didn't work quite right with temp tables, either).
Then I'd turn up the log level and detail, and see if I could find out
what statement was triggering the error report.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Amiel | 2010-06-08 13:26:25 | 3rd time is a charm.....right sibling is not next child crash. |
Previous Message | John T. Dow | 2010-06-08 12:37:02 | Re: Re: Error on Windows server could not open relation base/xxx/xxx Permission denied |