| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Beena Emerson <memissemerson(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: increasing the default WAL segment size |
| Date: | 2017-02-16 01:48:49 |
| Message-ID: | CA+TgmoaiTqo7PtftwPGqZLpXShps=krxhrK4L+n_zRByog4zmA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 15, 2017 at 8:46 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Now that we've renamed "xlog" to "wal" in user-facing elements, I think
> we should strive to use the name "wal" internally too in new code, not
> "xlog" anymore. This patch introduces several variables, macros,
> functions that ought to change names now -- XLogSegmentOffset should be
> WALSegmentOffset for example. (I expect that as we touch code over
> time, the use of "xlog" will decrease, though not fully disappear).
Ugh.
I think that's going to lead to a complete mess. We'll end up with
newer and older sections of the code being randomly inconsistent with
each other.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-02-16 01:54:51 | Re: increasing the default WAL segment size |
| Previous Message | Haribabu Kommi | 2017-02-16 01:48:34 | Re: Proposal: GetOldestXminExtend for ignoring arbitrary vacuum flags |