Re: Move vs. copy table between databases that share a tablespace?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Steven Lembark <lembark(at)wrkhors(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Move vs. copy table between databases that share a tablespace?
Date: 2019-04-03 14:55:49
Message-ID: 13608.1554303349@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I wrote:
> Steven Lembark <lembark(at)wrkhors(dot)com> writes:
>> Given that the two databases live in the same cluster and have
>> the owner & the tablespace in common, is there any way to move
>> the contents without a dump & reload?

> In principle you could do that; it's more or less the same thing that
> pg_upgrade --link does.

Actually, thinking about that a bit harder: there's one aspect of
what pg_upgrade does that's really hard to control from userspace,
and that's forcing tables to have the same OIDs as before. In this
context, that means you're probably out of luck if the table has a
TOAST table, unless the TOAST table is empty. There wouldn't be
any good way to keep TOAST pointers valid across the move.

(PG v12 will make that easier, but that's no help to you today.)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter J. Holzer 2019-04-03 14:57:58 Re: Recommendation to run vacuum FULL in parallel
Previous Message rihad 2019-04-03 14:49:02 Re: Recommendation to run vacuum FULL in parallel