From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <fujii(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Don't forget to flush XLOG_PARAMETER_CHANGE record. |
Date: | 2014-04-14 13:48:42 |
Message-ID: | CAHGQGwF0fexfOytRnca3FwFPuruVJLwbbOD+n9k9h8fF43Eefw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On Wed, Mar 26, 2014 at 5:39 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 25 March 2014 19:59, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> This commit message doesn't give any indication of what the
>>> consequences of this oversight are. I think that's generally a good
>>> thing to include.
>>
>> Yes, please. We (usually Bruce or I) make release notes based on the
>> commit logs. Please be sure your commit message includes enough info
>> to write a useful release note about the change.
>
> I don't think there are any consequences. All it seems to do is slow
> down recovery by an XLogFlush(), which admitedly isn't much
Yes. And basically the XLogFlush that the patch added is executed only
when wal_level is changed. It's not quite so common code path, I think.
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-04-14 14:45:17 | pgsql: Update list of relation types on which ALTER TABLE RENAME/OWNER |
Previous Message | Fujii Masao | 2014-04-14 13:33:55 | Re: pgsql: Don't forget to flush XLOG_PARAMETER_CHANGE record. |