Reply to list also.
Ccing list.
On 2/1/24 09:11, Johnathan Tiamoh wrote:
No. I have done any of this in the present cluster, I'm facing this issue.
Do you have some sort of replication or backup system running on this
cluster?
--
Adrian Klaver
adrian.kla...@aklaver.com
On 2/1/24 06:10, Johnathan Tiamoh wrote:
I haven't had difficulties in this cluster recently.
However I upgraded it from version 9.5 to 14.10 about 3 weeks ago.
Have you being doing any of the things that got you in trouble in this
thread:
https://www.postgresql.org/message-id/CACoPQdbEo
I haven't had difficulties in this cluster recently.
However I upgraded it from version 9.5 to 14.10 about 3 weeks ago.
On Thu, Feb 1, 2024 at 9:06 AM Jehan-Guillaume de Rorthais
wrote:
> On Thu, 1 Feb 2024 08:28:45 -0500
> Johnathan Tiamoh wrote:
>
> > Thank you Laurenz!
> >
> > Is there
On Thu, 1 Feb 2024 08:28:45 -0500
Johnathan Tiamoh wrote:
> Thank you Laurenz!
>
> Is there a way of preventing this from happening ?
This could either come from a hardware issue, or easily from your own actions
or procedures.
Did you have some difficulties with your instance lately? exception
Thank you Laurenz!
Is there a way of preventing this from happening ?
On Thu, Feb 1, 2024 at 2:36 AM Laurenz Albe
wrote:
> On Thu, 2024-02-01 at 00:48 -0500, Johnathan Tiamoh wrote:
> > I am having the following issue below. Please, I need help to fix it.
> >
> > ERROR: could not access stat
On Thu, 2024-02-01 at 00:48 -0500, Johnathan Tiamoh wrote:
> I am having the following issue below. Please, I need help to fix it.
>
> ERROR: could not access status of transaction 756525298
> Could not open file "pg_xact/02C8": No such file or directory.
That is data corruption, and you shoul
