From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Maksim(dot)Melnikov" <m(dot)melnikov(at)postgrespro(dot)ru> |
Subject: | Re: Persist injection points across server restarts |
Date: | 2025-06-03 17:17:25 |
Message-ID: | 71f54550c54d2505a538509631d1e1f3e3a1f602.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2025-06-03 at 13:13 +0900, Michael Paquier wrote:
> In all the approaches I've considered, this one was the least worst
> of
> all based on the point that all the complexity is hidden in the test
> module; there is no need to touch the backend code at all as long as
> there is a way to retrieve the list of points that would be dumped to
> disk.
True, though it does create a new file.
> Another set of test cases I had in mind was waits during recovery
> before consistency is reached. There is no way to add a point
> without
> connecting to the database, and we've had plenty of fixes involving
> the startup process and a different process, mostly the checkpointer.
> That's an annoying limitation.
If you have in mind some other ways to use it than I like it a lot
more. And I don't have a better idea.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2025-06-03 17:17:43 | Re: autoprewarm_dump_now |
Previous Message | Jeff Davis | 2025-06-03 17:11:17 | Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them |