Postgres Pro
Downloads
Home   >   mailing lists

BUG #17112: Sequence number is not restored when the stored procedure ends abnormally - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #17112: Sequence number is not restored when the stored procedure ends abnormally
Date
Msg-id 17112-7a61337ba5df1556@postgresql.org
Whole thread Raw
Responses Re: BUG #17112: Sequence number is not restored when the stored procedure ends abnormally  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-bugs
Tree view 
The following bug has been logged on the website:

Bug reference:      17112
Logged by:          Yuetsuro Kobayashi
Email address:      inconvenience.notice@gmail.com
PostgreSQL version: 13.3
Operating system:   Windows 10 Pro
Description:

When process was abnormal ends by a stored procedure processing problem, the
table processing is restored, but sequence number remains incremented and is
not restored.

pgsql-bugs by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size