Re: [HACKERS] Logical Replication WIP
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] Logical Replication WIP |
Дата | |
Msg-id | bfec23ec-108b-83d2-b60e-7271b5375318@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Logical Replication WIP (Petr Jelinek <petr.jelinek@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Logical Replication WIP
|
Список | pgsql-hackers |
0005-Add-separate-synchronous-commit-control-for-logical--v16.patch.gz This looks a little bit hackish. I'm not sure how this would behave properly when either synchronous_commit or logical_replication_synchronous_commit is changed at run time with a reload. I'm thinking maybe this and perhaps some other WAL receiver settings should be properties of a subscription, like ALTER SUBSCRIPTION ... SET/RESET. Actually, maybe I'm a bit confused what this is supposed to achieve. synchronous_commit has both a local and a remote meaning. What behavior are the various combinations of physical and logical replication supposed to accomplish? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: