Re: proposal: session server side variables

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: session server side variables
Date: 2016-12-29 09:11:39
Message-ID: alpine.DEB.2.20.1612290959480.4911@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> There is big difference - you concept missing any safe point. You have to
> specify same information more times.

Not necessarily, and if so maybe twice. I'm ok to recognize that it is a
difference between both approaches, and an inconvenient of the one I'm
proposing. There also see inconvenients to the other design as well, so
there will not be any perfect solution, IMO. That is the point of
discussing.

> I am sorry, this discussion is in cycle - there is no sense to continue.

If the only open option is to agree with your initial design, then
obviously this is not a path for reaching a consensus.

Could you put your ideal (final) design proposition on the wiki page? That
would avoid repeating the same cyclic arguments, they would be written
only once...

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2016-12-29 09:13:37 Re: Support for pg_receivexlog --format=plain|tar
Previous Message Pavel Stehule 2016-12-29 09:00:05 Re: proposal: session server side variables