| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Beena Emerson <memissemerson(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Support for N synchronous standby servers - take 2 |
| Date: | 2015-08-04 06:34:24 |
| Message-ID: | CAB7nPqRr=_C8Z4JOUaF5LfX3k8jB1nn9tAjyBUgaWvV-6ev-6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 4, 2015 at 3:27 PM, Beena Emerson <memissemerson(at)gmail(dot)com> wrote:
> Michael Paquier wrote:
>> And this is the case of any format as well. String format validation
>> for a GUC occurs when server is reloaded or restarted, one advantage
>> of JSON is that the parser validator is already here, so we don't need
>> to reinvent a new machinery for that.
>
> IIUC correctly, we would also have to add additional code to check that that
> given JSON has the required keys and entries. For ex: The "group" mentioned
> in the "s_s_names" should be definied in the "groups" section, etc.
Yep, true as well.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2015-08-04 06:35:43 | Re: tablecmds.c and lock hierarchy |
| Previous Message | Michael Paquier | 2015-08-04 06:33:40 | Re: tablecmds.c and lock hierarchy |