From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Westermann <daniel(dot)westermann(at)dbi-services(dot)com> |
Subject: | Re: zheap: a new storage format for PostgreSQL |
Date: | 2018-11-05 03:00:15 |
Message-ID: | CAA4eK1Ln7G9rT210n5fuz3p3FVnCdoxBiWkYyLUsYFhCAGm_Sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Nov 3, 2018 at 9:30 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Fri, Nov 2, 2018 at 6:41 PM Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> > I'm sure
> > it's not the only place where we do something like this, and the other
> > places don't trigger the valgrind warning, so how do those places do
> > this? heapam seems to call fetch_att in the end, which essentially calls
> > Int32GetDatum/Int16GetDatum/CharGetDatum, so why not to use the same
> > trick here?
> >
>
> This is because, in zheap, we have omitted all alignment padding for
> pass-by-value types. See the description in my previous email [1]. I
> think here we need to initialize ret_datum at the beginning of the
> function unless you have some better idea.
>
I have pushed a fix on the above lines in zheap-branch, but I am open
to change it if you have better ideas for the same.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Haozhou Wang | 2018-11-05 03:24:33 | Re: Vacuum Full does not release the disk size space after delete from table |
Previous Message | Stephen Frost | 2018-11-05 02:44:27 | Re: pg_dump multi VALUES INSERT |