BUG #17112: Sequence number is not restored when the stored procedure ends abnormally

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: inconvenience(dot)notice(at)gmail(dot)com
Subject: BUG #17112: Sequence number is not restored when the stored procedure ends abnormally
Date: 2021-07-16 02:39:06
Message-ID: 17112-7a61337ba5df1556@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17112
Logged by: Yuetsuro Kobayashi
Email address: inconvenience(dot)notice(at)gmail(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2021-07-16 02:49:11 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Previous Message Kyotaro Horiguchi 2021-07-16 02:05:00 Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size