Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node
От | Marko Kreen |
---|---|
Тема | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
Дата | |
Msg-id | CACMqXCL7Ln5S+kXgvUCj9vL4jbA=10-h0jDkPF4iVXUejjBTvw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: [PATCH 10/16] Introduce the concept that wal has a
'origin' node
Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
Список | pgsql-hackers |
On Mon, Jun 18, 2012 at 6:35 PM, Simon Riggs <simon@2ndquadrant.com> wrote: > On 13 June 2012 19:28, Andres Freund <andres@2ndquadrant.com> wrote: >> This adds a new configuration parameter multimaster_node_id which determines >> the id used for wal originating in one cluster. > > Looks good and it seems this aspect at least is commitable in this CF. > > Design decisions I think we need to review are > > * Naming of field. I think origin is the right term, borrowing from Slony. I have not read too deeply here, so maybe I am missing some important detail here, but idea that users need to coordinate a integer config parameter globally does not sound too attractive to me. Why not limit integers to local storage only and map them to string idents on config, UI and transport? -- marko
В списке pgsql-hackers по дате отправления: