Re: transactional swap of tables - Mailing list pgsql-general

From Kevin Grittner
Subject Re: transactional swap of tables
Date
Msg-id 1373639089.44097.YahooMailNeo@web162905.mail.bf1.yahoo.com
Whole thread Raw
In response to  (Vincenzo Romano <vincenzo.romano@notorand.it>)
Responses Re: transactional swap of tables
Re: transactional swap of tables
List pgsql-general
Vincenzo Romano <vincenzo.romano@notorand.it> wrote:

> I'd like to "replace" a full table F with an empty one E.
> In order to do this I see only one way:
>
> ALTER TABLE F RENAME TO T;
> ALTER TABLE E RENAME TO F;
> ALTER TABLE T RENAME TO E; -- optional
>
> This implies there's a moment when the full table doesn't exist.
> Would a transaction enclosure ensure that the table F will be
> always available to all clients?

Yes.  What you show is safe.  What has a race condition is dropping
the old table before all transactions which started with it have
completed.  If you're going to drop the old table, be sure to wait
long enough after the COMMIT for things to "settle".

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-general by date:

Previous
From: Melvin Call
Date:
Subject: Distributed systems and primary keys
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Distributed systems and primary keys