| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Wael Khobalatte <wael(at)vendr(dot)com> |
| Cc: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Persistent changes in rolled-back transactions |
| Date: | 2022-11-10 01:20:22 |
| Message-ID: | CAKFQuwbDY_0bzKLcjFxdTZekaknD_1=ELfHv5LEjMGTo6FgcvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Nov 9, 2022 at 6:16 PM Wael Khobalatte <wael(at)vendr(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-11-10 01:23:35 | Re: Persistent changes in rolled-back transactions |
| Previous Message | Wells Oliver | 2022-11-10 01:18:54 | Re: Persistent changes in rolled-back transactions |