RE: [PoC] pg_upgrade: allow to upgrade publisher node
От | Hayato Kuroda (Fujitsu) |
---|---|
Тема | RE: [PoC] pg_upgrade: allow to upgrade publisher node |
Дата | |
Msg-id | TYAPR01MB5866EEF603F76F34AA5D516CF5749@TYAPR01MB5866.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | RE: [PoC] pg_upgrade: allow to upgrade publisher node ("Wei Wang (Fujitsu)" <wangw.fnst@fujitsu.com>) |
Список | pgsql-hackers |
Dear Wang, > I'm not sure if there is any reason to not expose this new option? Do we have > concerns that users who use this new option by mistake may cause data > inconsistencies? > > BTW, I think that all options of pg_dump (please see the array of long_options > in the main function of the pg_dump.c file) are currently exposed to the user. Apart from another database object, --logical-replication-slot-only does not provide the "perfect" copy. As you might know, some attributes like xmin and restart_lsn are not copied, it just creates similar replication slots which have same name, plugin, and options. I think these things may be confused for users. Moreover, I cannot come up with use-case which DBAs use the option alone. If there is a good one, I can decide to remove the limitation. Best Regards, Hayato Kuroda FUJITSU LIMITED
В списке pgsql-hackers по дате отправления: