| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Speedup twophase transactions |
| Date: | 2016-01-11 21:46:01 |
| Message-ID: | CANP8+jJmxvpnZZGt2GUHst39q+4+VCtR6WffgJCqv+wq8tgQuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11 January 2016 at 20:10, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On January 11, 2016 8:57:58 PM GMT+01:00, Simon Riggs
> <simon(at)2ndQuadrant(dot)com> wrote:
> >On 11 January 2016 at 18:43, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> >It's clear there are various additional tuning opportunities, but the
> >objective of the current patch to improve performance is very, very
> >clearly
> >met, so I'm aiming to commit *this* patch soon.
>
> Again, the WAL read routine used doesn't deal with timeline changes.
Not relevant: The direct WAL read routine is never used during replay, so
your comment is not relevant since we don't change timelines on the master.
So no, it's bit ready to be committed.
>
I will update the comment on that function to explain its usage and its
limitations for future usage, to make that clearer.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-01-11 22:24:45 | Re: Speedup twophase transactions |
| Previous Message | Simon Riggs | 2016-01-11 21:35:58 | Re: PATCH: add pg_current_xlog_flush_location function |