Re: Persistent changes in rolled-back transactions

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Persistent changes in rolled-back transactions
Дата
Msg-id CAKFQuwbDY_0bzKLcjFxdTZekaknD_1=ELfHv5LEjMGTo6FgcvQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Persistent changes in rolled-back transactions  (Wael Khobalatte <wael@vendr.com>)
Список pgsql-admin
On Wed, Nov 9, 2022 at 6:16 PM Wael Khobalatte <wael@vendr.com> wrote:
> I've noticed serials still maintain incremented values even when a transaction is rolled back. Are there other similar persistent changes to be aware of?

Postgres sequences (what backs the serial type) are non-transactional. nextval, setval, et al. Truncate is also non-transactional. 

Truncate is transactional, it is not MVCC compliant though.

Writing data out to file on the filesystem, using dblink and opening a new session in a different database and doing work there are both case where the actions cross the system boundary that the transaction is able to control.

David J.

В списке pgsql-admin по дате отправления:

Предыдущее
От: Wells Oliver
Дата:
Сообщение: Re: Persistent changes in rolled-back transactions
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: Persistent changes in rolled-back transactions