Re: Support for N synchronous standby servers
От | Michael Paquier |
---|---|
Тема | Re: Support for N synchronous standby servers |
Дата | |
Msg-id | CAB7nPqTaL0M9FRbinBgJ3+MJe4Zs+o=0037kK4YZ3P_GOAT01A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Support for N synchronous standby servers (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Support for N synchronous standby servers
|
Список | pgsql-hackers |
On Tue, Sep 16, 2014 at 5:25 AM, Robert Haas <robertmhaas@gmail.com> wrote: > On Mon, Sep 15, 2014 at 3:00 PM, Michael Paquier > <michael.paquier@gmail.com> wrote: >> At least a set of hooks has the merit to say: do what you like with >> your synchronous node policy. > > Sure. I dunno if people will find that terribly user-friendly, so we > might not want that to be the ONLY thing we offer. Well, user-friendly interface is actually the reason why a simple GUC integer was used in the first series of patches present on this thread to set as sync the N-nodes with the lowest priority. I could not come up with something more simple. Hence what about doing the following: - A patch refactoring code for pg_stat_get_wal_senders and SyncRepReleaseWaiters as there is in either case duplicated code in this area to select the synchronous node as the one connected with lowest priority - A patch defining the hooks necessary, I suspect that two of them are necessary as mentioned upthread. - A patch for a contrib module implementing an example of simple policy. It can be a fancy thing with a custom language or even a more simple thing. Thoughts? Patch 1 refactoring the code is a win in all cases. Regards, -- Michael
В списке pgsql-hackers по дате отправления: