Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement
Date
Msg-id 18556.1223295799@sss.pgh.pa.us
Whole thread Raw
In response to Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> The trivial fix is to just force a checkpoint in ALTER TABLE SET 
> TABLESPACE. Can we do better than that? Perhaps only force a checkpoint 
> when we find that the file already exists.

If ALTER TABLE SET TABLESPACE is assuming that it can always use the
same relfilenode number in the new space as in the old, it's just plain
broken.  We need to fix that assumption.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Add relation fork support to pg_relation_size() function.
Next
From: Tom Lane
Date:
Subject: Re: About postgresql8.3.3 build in MS VS2005