| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Wraparound warning |
| Date: | 2016-10-25 17:19:26 |
| Message-ID: | CA+TgmoYFLw_T_c7hgTtdCv_N2dH+gkA94H3Jees1LXwipOFLTQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 25, 2016 at 11:20 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Do we still need to report the wraparound warning on server startup?
>
> LOG: MultiXact member wraparound protections are now enabled
>
> I thought that was going to be removed at some point, no?
If you start with a 9.3.small cluster and do a pg_upgrade to 10, you
could end up not seeing that message and not having those protections
enabled, and it would be useful to be able to tell that from looking
at the log.
Maybe what we should do (since this message obviously annoys everyone)
is change things so that, starting in v10, a message is logged at
startup if those protections are NOT enabled, and nothing is logged if
they are enabled. Keep the message for the case where protections are
enabled later, after startup time.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-10-25 17:23:51 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Tom Lane | 2016-10-25 17:18:47 | Re: Proposal: scan key push down to heap [WIP] |