| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | shihao zhong <zhong950419(at)gmail(dot)com>, Greg Burd <greg(at)burd(dot)me> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, andres(at)anarazel(dot)de, michael(at)paquier(dot)xyz, 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-29 20:33:29 |
| Message-ID: | 7881a505a3ce607f3c66c2f14abed9a1c4bcdf8d.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2026-10-27 at 10:04 -0400, shihao zhong wrote:
> I agree with that and I would like to spend some time to
> modernize hash,
There have been prior efforts in this area, such as WAL logging, under
the same assumption: that people don't use hash indexes, but would if
we put more work into them.
At this point, the bar is quite high for convincing people to use them.
Being slightly better in some cases is probably not enough to get
attention. As Andres said, the long keys problem with btrees is
incidental, and can be solved other ways. Also, btree indexes aren't
standing still, which makes it even harder to make the case.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Burd | 2026-10-29 20:36:31 | Re: index prefetching |
| Previous Message | Yash Jadhav | 2026-10-29 19:23:20 | Re: Proposal: Include CHECK constraint expression in violation error DETAIL |