Re: Fastpath while arranging the changes in LSN order in logical decoding - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Fastpath while arranging the changes in LSN order in logical decoding
Date
Msg-id CAFiTN-u4Moof3EzvxWCCxAc-cxGU3sYNSNGeMYpG=Oj4-O0q1Q@mail.gmail.com
Whole thread Raw
In response to Re: Fastpath while arranging the changes in LSN order in logicaldecoding  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Fastpath while arranging the changes in LSN order in logical decoding  (David Zhang <david.zhang@highgo.ca>)
Re: Fastpath while arranging the changes in LSN order in logicaldecoding  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers


On Wed, 8 Jan 2020 at 5:28 PM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
On 25/11/2019 05:52, Dilip Kumar wrote:
> In logical decoding, while sending the changes to the output plugin we
> need to arrange them in the LSN order.  But, if there is only one
> transaction which is a very common case then we can avoid building the
> binary heap.  A small patch is attached for the same.

Does this make any measurable performance difference? Building a
one-element binary heap seems pretty cheap.

I haven’t really measured the performance for this.  I will try to do that next week.  Thanks for looking into this.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: remove separate postgres.(sh)description files
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Block level parallel vacuum