pg_restore (fromuser -> touser)

Поиск
Список
Период
Сортировка
От Mayan
Тема pg_restore (fromuser -> touser)
Дата
Msg-id CAOeXn7o5qOF4kJMthdh4AWE6UxqQw=-_xvT7kF2vmASorUWWJg@mail.gmail.com
обсуждение исходный текст
Ответы Re: pg_restore (fromuser -> touser)  (Ninad Shah <nshah.postgres@gmail.com>)
Re: pg_restore (fromuser -> touser)  (Ben Madin <ben@ausvet.com.au>)
Список pgsql-general

Hi,

 

I had a general question about a feature that we depended on heavily when using other RDBMS providers which was the ability to take a schema dump and restore it to a different database and a different schema in that database (could be to the same database as well).  Basically, there was an option on restore to specify a FROMUSER and a TOUSER directive so schema A could be restored elsewhere but as schema B.

 

I don’t see such an option in Postgres and the only workaround I am aware of is to do a plain-text (format=p) and then a crude find/replace to replace the old schema name with the new schema name.  I’ve never actually tested this to be sure even this would work.  Also, using this option will prevent us from parallelizing the import or export, so it’s really not something we want to do.

 

This would be a really useful feature in my opinion along with the ability to maintain parallelization options. 

 

Are there any such features on the roadmap?  Is my understanding correct about the available ways to accomplish this – again, in a practical and performant way?

 

Thanks,

Mayan

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

Предыдущее
От: Ninad Shah
Дата:
Сообщение: Re: Why does VACUUM FULL pg_class sometimes wait for ShareLock on another transaction after getting AccessExclusiveLock on pg_class?
Следующее
От: Ninad Shah
Дата:
Сообщение: Re: PostgreSQL 9.2 high replication lag