| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Configuration Parameter/GUC value validation hook |
| Date: | 2022-05-06 09:43:24 |
| Message-ID: | CA+TgmoZRMv7+N+UoWvx8y84LGGjAg9LWVMFHdfoM0Byt-8YR0w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 4, 2022 at 7:12 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> Thanks Tom and Robert for your responses.
>
> How about we provide a sample extension (limiting some important
> parameters say shared_buffers, work_mem and so on to some
> "reasonable/recommended" limits) in the core along with the
> set_config_option_hook? This way, all the people using open source
> postgres out-of-the-box will benefit and whoever wants, can modify
> that sample extension to suit their needs. The sampe extension can
> also serve as an example to implement set_config_option_hook.
>
> Thoughts?
Well, it's better than just adding a hook and stopping, but I'm not
really sure that it's as good as what I'd like to have.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2022-05-06 10:08:01 | Re: postgres_fdw: commit remote (sub)transactions in parallel during pre-commit |
| Previous Message | David Rowley | 2022-05-06 09:27:57 | Re: strange slow query - lost lot of time somewhere |