| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Beena Emerson <memissemerson(at)gmail(dot)com>, "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:54:51 |
| Message-ID: | 20170216015451.qao2h5dhgmfqseqd@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-02-15 22:46:38 -0300, Alvaro Herrera 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).
I think this will just decrease the consistency in xlog.c (note the
name) et al.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-02-16 01:55:02 | Re: [Bug fix] PQsendQuery occurs error when target_session_attrs is set to read-write |
| Previous Message | Robert Haas | 2017-02-16 01:48:49 | Re: increasing the default WAL segment size |