| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: initdb recommendations |
| Date: | 2019-04-05 20:58:11 |
| Message-ID: | f27d3170-76cf-4afb-1e1a-b1059295ec8d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 2019-04-05 18:11, Jonathan S. Katz wrote:
> (There could be an additional discussion about whether or not we want to
> change the default behavior for initdb, but I would suggest that a safe
> starting point would be to ensure we call this out)
I think we should just change the defaults. There is a risk of warning
fatigue. initdb does warn about this, so anyone who cared could have
gotten the information.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2019-04-05 21:19:28 | Re: initdb recommendations |
| Previous Message | Jonathan S. Katz | 2019-04-05 16:11:31 | initdb recommendations |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-04-05 21:16:11 | Re: Re: Copy function for logical replication slots |
| Previous Message | Peter Eisentraut | 2019-04-05 20:46:28 | Re: monitoring CREATE INDEX [CONCURRENTLY] |