From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
Date: | 2015-11-02 07:09:59 |
Message-ID: | CAB7nPqR+VOUvOTwk5kxb2Tn7-JXXdtq3AkTcwjEdEL_tdBXp7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Mon, Nov 2, 2015 at 2:58 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> Simple patch, applies and makes cleanly, does what it says and says what it does.
>
> If a transaction holding locks aborts on an otherwise idle server, perhaps it will take a very long time for a log-shipping standby to realize this. But I have hard time believing that anyone who cares about that would be using log-shipping (rather than streaming) anyway.
>
> Marking it ready for committer.
>
> The new status of this patch is: Ready for Committer
Thanks! That was deadly fast.
Just wondering: shouldn't we keep the discussion around this patch on
-bugs instead? Not saying you are wrong, Jeff, I am just not sure what
would be the best practice regarding patches related to bugs. I would
think that it is at least necessary to keep the person who reported
the bug in CC to let him know the progress though.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2015-11-02 07:34:35 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
Previous Message | Michael Paquier | 2015-11-02 06:56:59 | Re: BUG #13741: vacuumdb does not accept valid password |
From | Date | Subject | |
---|---|---|---|
Next Message | YuanyuanLiu | 2015-11-02 07:27:28 | Re: Why not to use 'pg_ctl start -D ../data' to register posgtresql windows service |
Previous Message | Michael Paquier | 2015-11-02 06:56:59 | Re: BUG #13741: vacuumdb does not accept valid password |