Re: Copy entire schema A to a different schema B

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Tiffany Thang <tiffanythang(at)gmail(dot)com>, Jiří Fejfar <jurafejfar(at)gmail(dot)com>
Cc: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Copy entire schema A to a different schema B
Date: 2019-02-21 20:23:10
Message-ID: 982d6248-bff9-6233-6fd4-f46e0f2ebf7d@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/21/19 11:52 AM, Tiffany Thang wrote:
> Thanks everyone. Unfortunately the schema rename would not work since
> the source database will be our production system. We have not gone live
> yet but the system is expected to be constantly used.
>
> I have multiple tables that I need to export ranging from 20GB to 60GB
> each. The parallel will not work for a single table but would be
> beneficial if I have multiple tables to dump.
>
> I'm thinking maybe using what Adrian has suggested with the -f option
> and then modify the file or maybe use a common public schema everywhere
> on the source and target databases. I would have to restrict who has
> access to the public schema.

You can further break this down by using -s and -a switches to only work
with the table definitions and table data respectively. This can also be
done on the pg_dump end.

>
> Thanks.
>
> Tiff
>

> >> --
> >> Adrian Klaver
> >> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tamás András Kálmán 2019-02-21 21:07:59 Re: [GENERAL] Modified rows are not marked as dead and as such vacuum is unable to clean them up
Previous Message dangal 2019-02-21 19:59:18 Hot_standby_feedback = on