From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | depesz(at)depesz(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: WAL segments removed from primary despite the fact that logical replication slot needs it. |
Date: | 2022-10-18 11:21:26 |
Message-ID: | CAA4eK1Jc6Q2p=L36iEFgKYW1V2Rz3nKRpJdtmhg60za5bBK5WQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Oct 17, 2022 at 12:23 PM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
>
> At Sun, 16 Oct 2022 10:35:17 +0530, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote in
> > On Wed, Oct 5, 2022 at 8:54 PM hubert depesz lubaczewski
> > > So, 4 files are missing.
> > >
> > > These were archived properly, and I tried to restore them from archive, and put
> > > them in pg_wal, but even then pg12 was rejecting tries to connect to focal14
> > > slot with the same message about "requested WAL segment
> > > 000000010000CA0A00000049 has already been removed"
> > >
> >
> > I think you are seeing this behavior because we update the
> > lastRemovedSegNo before removing files in RemoveOldXlogFiles() and
> > then we use that to give the error you are seeing.
>
> lastRemovedSegNo is updated once per one segment of removal. Four
> files are lost in this case.
>
I didn't understand your response. I was saying the one possible
reason why even after restoring files from the archive the error
appears is because of the lastRemovedSegNo related check in function
CheckXLogRemoved() and we update its value while removing old xlog
files. From this behavior, it appears that somehow the server has only
removed those files even though the reason is not clear yet.
--
With Regards,
Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-10-18 11:27:52 | Re: WAL segments removed from primary despite the fact that logical replication slot needs it. |
Previous Message | PG Bug reporting form | 2022-10-18 09:17:05 | BUG #17649: With libpg5 15.0 psql 10.22 uses HOME variable instead of uid and /etc/passwd to select .pgpass file |