Re: Incorrect cost for MergeAppend
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Alexander Kuzmenkov <akuzmenkov@timescale.com>,
Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>,
David Rowley <dgrowleyml@gmail.com>, pgsql-hackers@postgresql.org
Date: 2024-01-31T15:31:57Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes: > Since we have a minor coming up very soon, I think it's not a good idea > to backpatch right now. Maybe you can push to master now, and consider > whether to backpatch later. As a rule, we don't back-patch changes like this ever. People don't appreciate plans changing in minor releases. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix costing bug in MergeAppend
- 9d1a5354f58c 17.0 landed
-
Fix locking when fixing an incomplete split of a GIN internal page
- 6a1ea02c491d 17.0 cited