Re: proposal: schema variables

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Erik Rijkers <er(at)xs4all(dot)nl>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, DUVAL REMI <REMI(dot)DUVAL(at)cheops(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: proposal: schema variables
Date: 2024-11-20 14:14:55
Message-ID: CAB-JLwYMw1pORoZxA9XeR52Svps6ah=ATgRDHdGQBT+j+Uy7qQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Em qua., 20 de nov. de 2024 às 10:52, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
escreveu:

> COMMIT can be a little bit messy. TRANSACTION END is more intuitive, I
> think.
>
>>
Exactly to be not messy I would just ON COMMIT for all, and DOCs can
explain that this option is ignored for temp objects and do the same at the
end of transaction, independently if commited or rolled back

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2024-11-20 14:20:18 Re: per backend I/O statistics
Previous Message Bertrand Drouvot 2024-11-20 14:10:23 Re: per backend I/O statistics

Browse pgsql-performance by date

  From Date Subject
Next Message Pavel Stehule 2024-11-20 14:57:23 Re: proposal: schema variables
Previous Message Pavel Stehule 2024-11-20 13:52:16 Re: proposal: schema variables