Re: Changing types of block and chunk sizes in memory contexts

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Changing types of block and chunk sizes in memory contexts
Date: 2023-07-16 23:18:38
Message-ID: CAApHDvokXXRmRjSwT59+c1nNntkmQPvDwLkk+phTCNdRDi_vBg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 14 Jul 2023 at 18:53, Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com> wrote:
> David Rowley <dgrowleyml(at)gmail(dot)com>, 13 Tem 2023 Per, 08:04 tarihinde şunu yazdı:
>>
>> I looked at your v2 patch. The only thing that really looked wrong
>> were the (Size) casts in the context creation functions. These should
>> have been casts to uint32 rather than Size. Basically, all the casts
>> do is say to the compiler "Yes, I know this could cause truncation due
>> to assigning to a size smaller than the source type's size". Some
>> compilers will likely warn without that and the cast will stop them.
>> We know there can't be any truncation due to the Asserts. There's also
>> the fundamental limitation that MemoryChunk can't store block offsets
>> larger than 1GBs anyway, so things will go bad if we tried to have
>> blocks bigger than 1GB.
>
>
> Right! I don't know why I cast them to Size. Thanks for the fix.

Pushed.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-07-17 01:16:02 Re: Autogenerate some wait events code and documentation
Previous Message Arne Roland 2023-07-16 22:42:42 Re: Permute underscore separated components of columns before fuzzy matching