Re: Re: [HACKERS] proposal: schema variables

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: David Steele <david(at)pgmasters(dot)net>, Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: Re: [HACKERS] proposal: schema variables
Date: 2019-03-07 08:37:58
Message-ID: CAFj8pRAy7qAbtQ9bnMCsDjRZR2T7c-XzQRsOtnngaaZRfG2wkQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Hi

>> My strong opinion based on the underlying use case is that it that such
>> session variables should be transactional by default, and Pavel strong
>> opinion is that they should not, to be closer to Oracle comparable
>> feature.
>
>
It is closer to any known database Oracle, DB2, Firebird, MSSQL, MySQL,

Regards

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-03-07 08:40:36 Re: Making all nbtree entries unique by having heap TIDs participate in comparisons
Previous Message Peter Geoghegan 2019-03-07 08:37:43 Re: Making all nbtree entries unique by having heap TIDs participate in comparisons

Browse pgsql-performance by date

  From Date Subject
Next Message David Steele 2019-03-07 09:26:06 Re: [HACKERS] proposal: schema variables
Previous Message Pavel Stehule 2019-03-07 08:32:25 Re: Re: [HACKERS] proposal: schema variables