Re: Catalog_xmin is not advanced when a logical slot is lost - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Catalog_xmin is not advanced when a logical slot is lost
Date
Msg-id 20221121181113.dpxbj6c4vm7dntpc@alvherre.pgsql
Whole thread Raw
In response to Re: Catalog_xmin is not advanced when a logical slot is lost  (sirisha chamarthi <sirichamarthi22@gmail.com>)
Responses Re: Catalog_xmin is not advanced when a logical slot is lost
List 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)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Prevent instability in contrib/pageinspect's regression test.
Next
From: Andres Freund
Date:
Subject: Re: Damage control for planner's get_actual_variable_endpoint() runaway