From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Function to track shmem reinit time |
Date: | 2018-03-28 18:55:21 |
Message-ID: | 5f4a346d-d066-22aa-f4bc-f03b62426600@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/4/18 11:17 AM, Tomas Vondra wrote:
>
> Furthermore, the patch is yet another victim of fd1a421fe - fixing the
> pg_proc entries is trivial, but a new version is needed.
>
> I'd also like to see an example/explanation how this improves this
> situation compared to only having pg_postmaster_start_time.
>
> So I'm setting this as waiting on author for now.
I'm not sure why this was set back to Needs Review since it neither
applies cleanly nor builds.
I'm setting this entry to Waiting on Author, but based on the discussion
I think it should be Returned with Feedback.
Regards,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2018-03-28 19:04:58 | Re: [bug fix] pg_rewind creates corrupt WAL files, and the standby cannot catch up the primary |
Previous Message | Peter Eisentraut | 2018-03-28 18:41:24 | Re: PL/pgSQL nested CALL with transactions |