Postgres Pro
Downloads
Home   >   mailing lists

Re: Question about VACUUM behavior with sub-transactions in stored procedures - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Question about VACUUM behavior with sub-transactions in stored procedures
Date
Msg-id CAKFQuwabMFmHtNicAi1QUJB+Q6PZn1twh2zfwqFX1_81moMXQw@mail.gmail.com
Whole thread Raw
In response to Question about VACUUM behavior with sub-transactions in stored procedures  (Кириллов Вячеслав <vkirillov@diasoft.ru>)
Responses Re: Question about VACUUM behavior with sub-transactions in stored procedures
List pgsql-hackers
Tree view
On Monday, October 21, 2024, Кириллов Вячеслав <vkirillov@diasoft.ru> wrote:

I have a question regarding the behavior of the auto VACUUM in PostgreSQL in the context of using stored procedures with sub-transactions.


This is a general usage inquiry not suited to discussion on -hackers.  We have a -general mailing list to discuss how to use the product.  This list is for discussing patches.

Here is the scenario: we have several stored procedures that modify or update table data. These procedures use sub-transactions, which are committed via COMMIT.


This isn’t how sub-transactions work.  They are created mainly by save points and are not independently committed (by the user in SQL).  What you are using are full transactions.


David J.

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Next
From: Ashutosh Bapat
Date:
Subject: Re: [PATCH] Add array_reverse() function