Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.
Date
Msg-id CAB7nPqSwEsqj4LNJDdCViYUqeO9aBY_x2L1eG+CArU1KktE_Qw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable.  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: [HACKERS] [PATCH v1] Add and report the new "in_hot_standby" GUCpseudo-variable.  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Oct 2, 2017 at 4:16 PM, Daniel Gustafsson <daniel@yesql.se> wrote:
> Based on the unaddressed questions raised in this thread, I’m marking this
> patch Returned with Feedback.  Please re-submit a new version of the patch to a
> future commitfest.

For some reason this patch has been moved to CF 2017-11, but there has
been no real updates since the last version in

https://www.postgresql.org/message-id/flat/1572601.d6Y6hSXNBC%40hammer.magicstack.net#1572601.d6Y6hSXNBC@hammer.magicstack.net
was sent. The patch fails to apply as well now. I am marking it as
returned with feedback. I am not seeing any replies to the requests
done as well.
--
Michael


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means
Next
From: Etsuro Fujita
Date:
Subject: Re: [HACKERS] Bug in ExecModifyTable function and trigger issuesfor foreign tables