From: | Дмитрий Воронин <carriingfate92(at)yandex(dot)ru> |
---|---|
To: | Victor Drobny <v(dot)drobny(at)postgrespro(dot)ru> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump issues |
Date: | 2017-07-26 11:56:27 |
Message-ID: | 1999271501070187@web36o.yandex.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
25.07.2017, 11:17, "Victor Drobny" <v(dot)drobny(at)postgrespro(dot)ru>:
>
> Hello,
>
> Do you expect to have some flag like '--rename=test->test2'?
Yes, I do.
> Will dump with test replaced by test2(of course only in related places)
> be valid dump in this case?
Yes, it will.
> What is the possible scenario for the renaming option? Is it doing to be
> dumping of the one schema only?
> Or it could be dump of database? In this case pg_dump should also
> support multiple rules for renaming.
pg_dump scans dumped objects and rename them by rules, that could be set by pg_dump argument line options.
As I now, pg_dump and pg_restore use the same functions, so, renaming mechanism can be integrated in pg_restore too.
pg_restore will scan dumped objects and rename them by rules.
In future, rules could be applied on all database objects.
>
> Thank you for attention!
>
> --
> ------
> Victor Drobny
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
--
Best regards, Dmitry Voronin
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-07-26 11:57:16 | Re: Change in "policy" on dump ordering? |
Previous Message | Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= | 2017-07-26 11:15:50 | Re: proposal: psql: check env variable PSQL_PAGER |