Re: Postgres PANIC when it could not open file in pg_logical/snapshots directory - Mailing list pgsql-general

From Vijaykumar Jain
Subject Re: Postgres PANIC when it could not open file in pg_logical/snapshots directory
Date
Msg-id CAM+6J9666SyCm9YoFQ7+UBR4Zb_G7ERiO=QP3HcdHnisFbX78g@mail.gmail.com
Whole thread Raw
In response to Postgres PANIC when it could not open file in pg_logical/snapshots directory  (Mike Yeap <wkk1020@gmail.com>)
List pgsql-general


On Thu, Jun 24, 2021, 9:28 AM Mike Yeap <wkk1020@gmail.com> wrote:
Hi Vijay, thanks for the tests, it's very helpful.

Just that, isn't it too extreme when one of the processes having problems accessing a snap file, it causes all other processes to be terminated? After all, most of the other processes do not need to access the snap files. Is there a way to fine tune this behaviour?

Thank you.

Regards,
Mike Yeap

I guess the best people to ask this question is the core team, I am just over a year in pg, I am not in a position to call this an issue with postgres unless I understand the underlying design and possible data corruption if any if it does not abort etc.
I'll leave it to the core team, then to give incorrect workaround.


pgsql-general by date:

Previous
From: Michael Ivanov
Date:
Subject: insert ..... returning problem
Next
From: Marc Mamin
Date:
Subject: removing "serial" from table definitions.