Re: BTMaxItemSize seems to be subtly incorrect - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: BTMaxItemSize seems to be subtly incorrect
Date
Msg-id CAH2-WznqLyWFK+Jkmsc+rTqPuzQCC_bw-6uxjjjNedr0R+Hg2A@mail.gmail.com
Whole thread Raw
In response to Re: BTMaxItemSize seems to be subtly incorrect  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: BTMaxItemSize seems to be subtly incorrect
List pgsql-hackers
On Thu, Aug 4, 2022 at 10:25 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> FYI florican and lapwing showed:
>
> 2022-08-05 01:04:29.903 EDT [34485:5] FATAL:  deduplication failed to
> add heap tid to pending posting list
> 2022-08-05 01:04:29.903 EDT [34485:6] CONTEXT:  WAL redo at 0/49708D8
> for Btree/DEDUP: nintervals 4; blkref #0: rel 1663/16384/2674, blk 1

This very likely has something to do with the way nbtdedup.c uses
BTMaxItemSize(), which apparently won't work on these 32-bit systems
now.

I'll fix this tomorrow morning.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BTMaxItemSize seems to be subtly incorrect
Next
From: Peter Smith
Date:
Subject: Re: Support logical replication of DDLs