| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Beena Emerson <memissemerson(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: increasing the default WAL segment size |
| Date: | 2017-01-05 15:40:17 |
| Message-ID: | CA+TgmoYNVeKa_gfRuA0C1mwzVAHkHT4MmEiS1tV=bEW_tGOoHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 5, 2017 at 6:39 AM, Beena Emerson <memissemerson(at)gmail(dot)com> wrote:
> This patch only needed the wal_segment_size and hence I made this specific
> command.
> How often and why would we need other parameter values in the replication
> connection?
> Making it a more general command to fetch any parameter can be a separate
> topic. If it gets consensus, maybe it could be done and used here.
I think the idea of supporting SHOW here is better than adding a
special-purpose command just for the WAL size.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-01-05 15:55:01 | Re: UNDO and in-place update |
| Previous Message | Pavel Stehule | 2017-01-05 14:20:32 | Re: generating fmgr prototypes automatically |