From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Missing break in RelationFindReplTupleSeq |
Date: | 2020-02-03 22:04:04 |
Message-ID: | 20200203220404.GA13588@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-Jan-31, Alvaro Herrera wrote:
> On 2020-Jan-31, Konstantin Knizhnik wrote:
>
> > Eventually we find out that logical replication in the current version of
> > Postgres works significantly slower on table with replica identity full than
> > old pglogical implementation.
> >
> > The comment to RelationFindReplTupleSeq says:
> >
> > Note that this stops on the first matching tuple.
> >
> > But actually this function continue traversal until end of the table even if
> > tuple was found.
> > I wonder if break; should be added to the end of for loop.
>
> Wow, you're right, and the "break" is missing there. I propose it like
> this.
Pushed, thanks for reporting.
I had one very strange thing happen while testing this -- I put the
tests to run in all branches in parallel, and they took about 12 minutes
to finish instead of the normal 5. I tried to repeat this result but
was unable to do so. My only hypothesis is that my laptop entered some
kind of low-performance mode.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2020-02-04 00:26:46 | Re: Is custom MemoryContext prohibited? |
Previous Message | Konstantin Knizhnik | 2020-02-03 20:56:11 | Re: Global temporary tables |