Re: Have better wording for snapshot file reading failure

Yogesh Sharma <yogesh.sharma@catprosystems.com>

From: Yogesh Sharma <yogesh.sharma@catprosystems.com>

To: pgsql-hackers@lists.postgresql.org

Date: 2023-09-17T12:36:06Z

Lists: pgsql-hackers

On 9/14/23 20:33, Andres Freund wrote:
> I'd probably just go for something like "snapshot \"%s\" does not exist",
> similar to what we report for unknown tables etc. Arguably changing the
> errcode to ERRCODE_UNDEFINED_OBJECT would make this more precise?

+1  better  informative message compare to the original patch.

-- 
Kind Regards,
Yogesh Sharma
PostgreSQL, Linux, and Networking Expert
Open Source Enthusiast and Advocate

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Improve error message for snapshot import in snapmgr.c, take two
- 78a33bba4c63 17.0 landed
Revert "Improve error message on snapshot import in snapmgr.c"
- bddbbdf99b16 11.22 landed
- 50d44c163352 12.17 landed
- f18efc6f2bc8 13.13 landed
- 1988f8766eeb 14.10 landed
- fe60434af76f 15.5 landed
- 3f94dfc00870 16.1 landed
- be022908cfe2 17.0 landed
Improve error message on snapshot import in snapmgr.c
- a4cef3384d6d 11.22 landed
- 33bc7d424695 12.17 landed
- d98cbea20125 13.13 landed
- a7b92d1c6807 14.10 landed
- 19885ab246d8 15.5 landed
- be3dfd3dff03 16.1 landed
- a0d87bcd9b57 17.0 landed