Re: Copy entire schema A to a different schema B

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: Copy entire schema A to a different schema B
Дата
Msg-id 982d6248-bff9-6233-6fd4-f46e0f2ebf7d@aklaver.com
обсуждение исходный текст
Ответ на Re: Copy entire schema A to a different schema B  (Tiffany Thang <tiffanythang@gmail.com>)
Ответы Re: Copy entire schema A to a different schema B  (Melvin Davidson <melvin6925@gmail.com>)
Список 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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com


В списке pgsql-general по дате отправления:

Предыдущее
От: dangal
Дата:
Сообщение: Hot_standby_feedback = on
Следующее
От: Tamás András Kálmán
Дата:
Сообщение: Re: [GENERAL] Modified rows are not marked as dead and as such vacuumis unable to clean them up