Re: WAL record CRC calculated incorrectly because of underlying buffer modification

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Greg Burd <greg(at)burd(dot)me>
Cc: pgsql-hackers(at)postgresql(dot)org, andres(at)anarazel(dot)de, michael(at)paquier(dot)xyz, pgsql(at)j-davis(dot)com, thomas(dot)munro(at)gmail(dot)com, exclusion(at)gmail(dot)com, amit(dot)kapila16(at)gmail(dot)com, hlinnaka(at)iki(dot)fi
Subject: Re: WAL record CRC calculated incorrectly because of underlying buffer modification
Date: 2026-10-27 14:04:58
Message-ID: CAGRkXqRWHGcb+hzxeJHzS8vmjQciqhaVvKBupHoHkhR7kEboyw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Greg,

> That's a signal to innovate, not remove code.

I agree with that and I would like to spend some time to modernize hash,
I will start looking after the PG19 release and happy to review any of your
hash changes.

> Expression indexes prevent HOT updates, so maybe you could but at what
> cost?

Haven't really tested that, just some wild thinking, but I think hash index
also
have similar limitations.

Thanks,
Shihao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2026-10-27 14:05:29 Re: Reject incompatible options specified with VACUUM ONLY_DATABASE_STATS
Previous Message Greg Burd 2026-10-27 13:54:47 Re: WAL record CRC calculated incorrectly because of underlying buffer modification