Re: post-freeze damage control - Mailing list pgsql-hackers

From David Steele
Subject Re: post-freeze damage control
Date
Msg-id cab01e3d-bf5d-4750-b67f-8c1b2f74d6ea@pgmasters.net
Whole thread Raw
In response to Re: post-freeze damage control  (Tom Kincaid <tomjohnkincaid@gmail.com>)
Responses Re: post-freeze damage control
List pgsql-hackers
On 4/11/24 10:23, Tom Kincaid wrote:
> 
> The extensive Beta process we have can be used to build confidence we 
> need in a feature that has extensive review and currently has no known 
> issues or outstanding objections.

I did have objections, here [1] and here [2]. I think the complexity, 
space requirements, and likely performance issues involved in restores 
are going to be a real problem for users. Some of these can be addressed 
in future releases, but I can't escape the feeling that what we are 
releasing here is half-baked.

Also, there are outstanding issues here [3] and now here [4].

Regards,
-David

[1] 
https://www.postgresql.org/message-id/590e3017-da1f-4af6-9bf0-1679511ca7e5%40pgmasters.net
[2] 
https://www.postgresql.org/message-id/11b38a96-6ded-4668-b772-40f992132797%40pgmasters.net
[3] 

https://www.postgresql.org/message-id/flat/05fb32c9-18d8-4f72-9af3-f41576c33119%40pgmasters.net#bb04b896f0f0147c10cee944a1391c1e
[4] 
https://www.postgresql.org/message-id/flat/9badd24d-5bd9-4c35-ba85-4c38a2feb73e%40pgmasters.net



pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Improve eviction algorithm in ReorderBuffer
Next
From: Tom Lane
Date:
Subject: Re: Issue with the PRNG used by Postgres