pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Johnathan Tiamoh <johnathantiamoh@gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: DETAIL: Could not open file "pg_xact/0EEA": No such file or directory
Date: Mon, 19 Feb 2024 11:45:13 -0800
Message-ID: <3f10ca94-4433-40b4-8060-3cc0225b3e2e@aklaver.com> (raw)
In-Reply-To: <CACoPQdauxFqNxNrg0BOn6f9PmnjcM+6ks0wyOUSVLQ-FWQxj5g@mail.gmail.com>
References: <CACoPQdZo8onyi=ri+SYgQ-qxs65SFpC=xQKU4fgC9qpHyvt_eQ@mail.gmail.com>
	<c2204df0-1195-4528-8080-8745ea20a806@aklaver.com>
	<CACoPQdauxFqNxNrg0BOn6f9PmnjcM+6ks0wyOUSVLQ-FWQxj5g@mail.gmail.com>

On 2/19/24 11:36, Johnathan Tiamoh wrote:

Reply to list also.
Cc'ing  list.

> Sorry  Adrian,
> 
> This is occurring at every checkpoint. This actually has to do with 
> Listen/Notify.
> It is not really linked to the upgrade per say.

I would say it is.

From:

https://www.postgresql.org/docs/current/storage-file-layout.html

pg_xact 	Subdirectory containing transaction commit status data

I'm guessing what ever process you used to upgrade did not transfer all 
the files. Or you have some ongoing process that is removing the files 
prematurely.

> 
>   However, This is occurring in clusters that I recently upgraded to 14.

Which contradicts, "It is not really linked to the upgrade per say.".

> 
> 
> 
> 
> On Mon, Feb 19, 2024 at 12:17 PM Adrian Klaver 
> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
> 
>     On 2/19/24 08:59, Johnathan Tiamoh wrote:
>      > Hello,
>      >
>      > Please, I need help in resolving this issue.  I recently upgraded to
>      > postgresql and have experienced the above error with 2 clusters 
>     already.
>      >
>      > I keep losing data in the pg_exact directory.
> 
>     We have been down this rabbit hole multiple times with your upgrading
>     procedures. By now you should know that the above does not qualify as
>     close to being a sufficient problem report. Respond with a complete
>     explanation of your setup and the commands run that got you into this
>     situation.
> 
> 
>      >
>      > Kind regards
>      > Johnathan T
> 
>     -- 
>     Adrian Klaver
>     adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (4+ messages)  latest in thread

Message-ID: <3f10ca94-4433-40b4-8060-3cc0225b3e2e@aklaver.com>
Permalink:  ../3f10ca94-4433-40b4-8060-3cc0225b3e2e@aklaver.com/
Also on:    postgresql.org/message-id/3f10ca94-4433-40b4-8060-3cc0225b3e2e@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, johnathantiamoh@gmail.com
  Subject: Re: DETAIL: Could not open file "pg_xact/0EEA": No such file or directory
  In-Reply-To: <3f10ca94-4433-40b4-8060-3cc0225b3e2e@aklaver.com>
  References: <CACoPQdZo8onyi=ri+SYgQ-qxs65SFpC=xQKU4fgC9qpHyvt_eQ@mail.gmail.com> <c2204df0-1195-4528-8080-8745ea20a806@aklaver.com> <CACoPQdauxFqNxNrg0BOn6f9PmnjcM+6ks0wyOUSVLQ-FWQxj5g@mail.gmail.com> <3f10ca94-4433-40b4-8060-3cc0225b3e2e@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox