From: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>, fabriziomello(at)gmail(dot)com, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Rahila Syed <rahila(dot)syed(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Minimal logical decoding on standbys |
Date: | 2022-12-15 10:20:18 |
Message-ID: | be50d6d6-ebb7-697d-282a-6cfdda5efc05@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 12/14/22 6:48 PM, Robert Haas wrote:
> On Wed, Dec 14, 2022 at 12:35 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
>>> typedef struct xl_heap_prune
>>>
>>> I think this is unsafe on alignment-picky machines. I think it will
>>> cause the offset numbers to be aligned at an odd address.
>>> heap_xlog_prune() doesn't copy the data into aligned memory, so I
>>> think this will result in a misaligned pointer being passed down to
>>> heap_page_prune_execute.
>>
>> I think the offset numbers are stored separately from the record, even
>> though it doesn't quite look like that in the above due to the way the
>> 'OFFSET NUMBERS' is embedded in the struct. As they're stored with the
>> block reference 0, the added boolean shouldn't make a difference
>> alignment wise?
>>
>> Or am I misunderstanding your point?
>
> Oh, you're right. So this is another case similar to
> xl_btree_reuse_page. In heap_xlog_prune(), we access the offset number
> data like this:
>
> redirected = (OffsetNumber *)
> XLogRecGetBlockData(record, 0, &datalen);
> end = (OffsetNumber *) ((char *) redirected + datalen);
> nowdead = redirected + (nredirected * 2);
> nowunused = nowdead + ndead;
> nunused = (end - nowunused);
> heap_page_prune_execute(buffer,
>
> redirected, nredirected,
> nowdead, ndead,
>
> nowunused, nunused);
>
> This is only safe if the return value of XLogRecGetBlockData is
> guaranteed to be properly aligned,
Why, could you please elaborate?
It looks to me that here we are "just" accessing the
members of the xl_heap_prune struct to get the numbers.
Then, the actual data will be read later in heap_page_prune_execute() from the buffer/page based on the numbers we got from xl_heap_prune.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Drouvot, Bertrand | 2022-12-15 10:31:42 | Re: Minimal logical decoding on standbys |
Previous Message | Nitin Jadhav | 2022-12-15 10:13:35 | Re: Inconsistency in reporting checkpointer stats |