| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fastpath while arranging the changes in LSN order in logical decoding |
| Date: | 2020-01-08 12:36:52 |
| Message-ID: | CAFiTN-u4Moof3EzvxWCCxAc-cxGU3sYNSNGeMYpG=Oj4-O0q1Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 8 Jan 2020 at 5:28 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-01-08 13:16:38 | Re: [HACKERS] Block level parallel vacuum |
| Previous Message | Heikki Linnakangas | 2020-01-08 12:33:23 | Re: remove separate postgres.(sh)description files |