From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Vladimir Borodin <root(at)simply(dot)name>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Improving replay of XLOG_BTREE_VACUUM records |
Date: | 2016-01-08 14:31:04 |
Message-ID: | CANP8+jJwjNSfJo8aDn4jB7WKvN3rPLfYoVXrFP36qnwuLBmYCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8 January 2016 at 13:36, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Vladimir Borodin wrote:
> >
> > > 7 янв. 2016 г., в 5:26, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
> написал(а):
> > >
> > > On Thu, Jan 7, 2016 at 12:20 AM, Alvaro Herrera
> > > <alvherre(at)2ndquadrant(dot)com <mailto:alvherre(at)2ndquadrant(dot)com>> wrote:
>
> > >> Would you please have a look at Simon's patch, in particular verify
> > >> whether it solves the performance dip in your testing environment?
> > >>
> https://www.postgresql.org/message-id/CANP8%2BjJuyExr1HnTAdZraWsWkfc-octhug7YPtzPtJcYbyi4pA%40mail.gmail.com
> > >> (Note there's an updated patch a few emails down the thread.)
> > >>
> > >> If it seems to fix the problem for you, I think we should mark yours
> > >> rejected and just apply Simon’s.
> >
> > Ok, I’ll try this patch with my use case. Basically, it’s not so easy
> > now since I’ve partitioned that big table to not have such problems
> > but there is a way to reproduce it once again. If it helps, I agree
> > that my should be rejected in favor of the Simon’s patch because my
> > patch just reduces replication lag but Simon’s seems to remove lag at
> > all.
>
> I would agree except for the observation on toast indexes. I think
> that's an important enough use case that perhaps we should have both.
>
The exclusion of toast indexes is something we can remove also, I have
recently discovered. When we access toast data we ignore MVCC, but we still
have the toast pointer and chunkid to use for rechecking our scan results.
So a later patch will add some rechecks.
So I don't think it is worth applying this patch now. I should add that I
also had a patch that did this, posted earlier IIRC. That is not the reason
to reject this, just me pointing out that I'm effectively rejecting my own
earlier patch also.
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2016-01-08 14:32:39 | Re: New feature "... ALTER CONSTRAINT ... VERIFY USING INDEX" |
Previous Message | Vitaly Burovoy | 2016-01-08 14:14:55 | Re: New feature "... ALTER CONSTRAINT ... VERIFY USING INDEX" |