| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | sirisha chamarthi <sirichamarthi22(at)gmail(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Subject: | Re: Catalog_xmin is not advanced when a logical slot is lost |
| Date: | 2022-11-21 18:11:13 |
| Message-ID: | 20221121181113.dpxbj6c4vm7dntpc@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)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(at)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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-11-21 18:17:05 | Re: Damage control for planner's get_actual_variable_endpoint() runaway |
| Previous Message | Tom Lane | 2022-11-21 18:08:58 | Re: pgsql: Prevent instability in contrib/pageinspect's regression test. |