Re: Using a lock to avoid: could not open relation with OID - Mailing list pgsql-general

From Craig Ringer
Subject Re: Using a lock to avoid: could not open relation with OID
Date
Msg-id 4B4BB378.4040003@postnewspapers.com.au
Whole thread Raw
In response to Using a lock to avoid: could not open relation with OID  (Francisco Reyes <lists@stringsutils.com>)
List pgsql-general
On 12/01/2010 2:04 AM, Francisco Reyes wrote:
> I need to replace a table with a new one.
> Example..
> I create a script that continously does selects like
> select count(*) from tmp_deleteme_francisco;
> .... enough selects to last the duration of second script
> select count(*) from tmp_deleteme_francisco;
>
>
> Another script then does
> begin;
> select * into tmp_deleteme_francisco_2 from xxx;
> alter table tmp_deleteme_francisco rename to tmp_deleteme_francisco_old;
> alter table tmp_deleteme_francisco_2 rename to tmp_deleteme_francisco;
> drop table tmp_deleteme_francisco_old;
> commit;
>
> That results in the script doing the selects getting could not open
> relation with OID ####.

Possible workaround: Instead of your table creation, renaming and
dropping, use TRUNCATE.

--
Craig Ringer

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: How to get DATE in server locale format
Next
From: Craig Ringer
Date:
Subject: Re: Database size