Re: [HACKERS] proposal: session server side variables - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] proposal: session server side variables
Date
Msg-id alpine.DEB.2.20.1702031039370.4856@lancre
Whole thread Raw
In response to Re: [HACKERS] proposal: session server side variables  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] proposal: session server side variables
Re: [HACKERS] proposal: session server side variables
List pgsql-hackers
> We can implement XA support for variables, ale I don't think so default 
> should be XA.

I was answering your question, which is what you can do about the 
feedback: take the one hard/strong point into account in your proposal.

You do not want to do that. Too bad.

The argument that you keep on repeating about "other software do it like 
that so it is the good way" do not work because these software (Oracle, 
DB2, ...) have features unavailable to postgres which mitigate the issue 
I'm raising, and there is no such mitigation in postgres.

Note that you can proceed and simply ignore my negative opinion, which 
will stay negative till these "secure" variables are transactional by 
default, or till nested/autonomous transactions are provided by postgres.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: [HACKERS] asynchronous execution
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal: session server side variables