hi,
thanks for taking a look.
> y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) writes:
>> the attached patch is to avoid unnecessary detoast'ing and EOF marker pages
>> when possible. does it make sense?
>
> The blob page size is already chosen not to allow for out-of-line
> storage, not to mention
hi,
> I wrote:
>> y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) writes:
>>> after systable_getnext_ordered returned NULL, is it ok to call it again?
>
>> I wouldn't rely on it working.
>
>>> i'm wondering because inv_truncate seems to do it and expecting NULL.
>
>> Hmm, that may well be a bug. Hav
y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) writes:
> the attached patch is to avoid unnecessary detoast'ing and EOF marker pages
> when possible. does it make sense?
The blob page size is already chosen not to allow for out-of-line
storage, not to mention that pg_largeobject doesn't have a TOAST t
I wrote:
> y...@mwd.biglobe.ne.jp (YAMAMOTO Takashi) writes:
>> after systable_getnext_ordered returned NULL, is it ok to call it again?
> I wouldn't rely on it working.
>> i'm wondering because inv_truncate seems to do it and expecting NULL.
> Hmm, that may well be a bug. Have you tested it?
