| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
| Cc: | cedric(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Christopher Browne <cbbrowne(at)gmail(dot)com> |
| Subject: | Re: Proposal for Allow postgresql.conf values to be changed via SQL |
| Date: | 2012-11-17 21:38:03 |
| Message-ID: | CAHGQGwHG1azOjUav69B6+r7tRXhuMz6CAPLYsYOPzBCg0yor0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 17, 2012 at 10:25 PM, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> 1. have a system table pg_global_system_settings(key,value)
Do we really need to store the settings in a system table?
Since WAL would be generated when storing the settings
in a system table, this approach seems to prevent us from
changing the settings in the standby.
> 2. On SQL command execution, insert if the value doesn't exist or update if
> already existing.
This means that we should implement something like MERGE
command first?
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-11-17 21:53:31 | Re: Do we need so many hint bits? |
| Previous Message | Jeff Davis | 2012-11-17 21:30:07 | Re: Do we need so many hint bits? |