From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Make tuple deformation faster |
Date: | 2024-12-02 14:03:55 |
Message-ID: | CAGnEbog92Og2CpC2S8=g_HozGsWtt_3kRS1sXjLz0jKSoCNfLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
пн, 2 дек. 2024 г. в 13:24, David Rowley <dgrowleyml(at)gmail(dot)com>:
> I ended up adjusting the code here so that TupleDescSize() returns the
> full size and TupleDescAttrAddress() manually calculates the offset to
> start the FormData_pg_attribute array. That allows
> TupleDescFullSize() to be deleted. I changed how TupleDescCopy()
> works as it used to perform the memcpy in 2 parts. I've changed that
> to now perform a single memcpy() and reset the ->attrs field after the
> memcpy so that it correctly points to the address for its own
> TupleDesc rather than the one from the source.
>
>
Nice!
> I've attached a v5 set of patches, which I think addresses everything
> you mentioned. I've also shuffled the patches around a little to how
> I think they should be committed.
>
I'm glad that the patch from “More tuple deformation speedups” is moved
here, I wanted
to mention that both patches should be committed together.
All is good, and the benefits are clearly visible (same setup used).
--
Victor Yegorov
Attachment | Content-Type | Size |
---|---|---|
image/jpeg | 54.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-12-02 14:14:11 | Re: Consider pipeline implicit transaction as a transaction block |
Previous Message | Dmitry Dolgov | 2024-12-02 13:44:48 | Re: Consider the number of columns in the sort cost model |