Re: Catalog_xmin is not advanced when a logical slot is lost
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: sirisha chamarthi <sirichamarthi22@gmail.com>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, pgsql-hackers@lists.postgresql.org, Amit Kapila <amit.kapila16@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Date: 2022-11-21T18:11:13Z
Lists: pgsql-hackers
On 2022-Nov-21, sirisha chamarthi wrote: > It appears to be. wal_sender is setting restart_lsn to a valid LSN even > when the slot is invalidated. > postgres@pgvm:~$ /usr/local/pgsql/bin/pg_receivewal -S s1 -D . > pg_receivewal: error: unexpected termination of replication stream: ERROR: > requested WAL segment 0000000100000000000000EB has already been removed > pg_receivewal: disconnected; waiting 5 seconds to try again > ^Cpostgres@pgvm:~$ /usr/local/pgsql/bin/psql > psql (16devel) > Type "help" for help. > > postgres=# select * from pg_replication_slots; > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. Whoa, I cannot reproduce this :-( -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Java is clearly an example of money oriented programming" (A. Stepanov)
Commits
-
Ignore invalidated slots while computing oldest catalog Xmin
- 36eeb37cd611 13.10 landed
- 1b3ed757145d 14.7 landed
- 1ad033df16df 15.2 landed
- 0557e1770230 16.0 landed