From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: add pg_current_xlog_flush_location function |
Date: | 2016-01-11 12:01:39 |
Message-ID: | 569399A3.3090401@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01/11/2016 06:30 AM, Michael Paquier wrote:
>
> Updating LogwrtResult directly when calling your new function
> GetXLogFlushRecPtr() does not strike me as a particularly good idea
> per this portion in XLogFlush():
>
> /* Quick exit if already known flushed */
> if (record <= LogwrtResult.Flush)
> return;
>
> The same counts for GetXLogWriteRecPtr, we had better allocate the
> value in an independent variable as there are checks using it. For
> now it does not matter much for the write position because all the
> code paths doing the checks explicitly update again the pointer
> before looking at it but it seems to me that using an independent
> variable would make the code more robust.
Why? LogwrtResult only serves as a local cache of shared values, so
there should be no danger of skipping something.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2016-01-11 12:51:31 | 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |
Previous Message | Magnus Hagander | 2016-01-11 11:36:44 | Re: Why doesn't src/backend/port/win32/socket.c implement bind()? |