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>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>
Subject: Re: proposal: session server side variables
Date: 2017-01-04 16:30:27
Message-ID: alpine.DEB.2.20.1701041720130.22281@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Now we can this feature emulate with dblink, and there are patches in
> commitfest based on background workers, and emulation will be cheaper.

I had not noticed that "background session" proposal. That's definitely an
interesting feature to have for some use cases. Dblink implies a new
connection I think, pretty expensive. I wish that the proposal would be
language independent, like DB2 simple AUTONOMOUS declaration on a
function. It seems quite heavily linked to PL/pgSQL right now.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-01-04 16:37:54 Re: [PATCH] Reload SSL certificates on SIGHUP
Previous Message Pavel Stehule 2017-01-04 16:30:07 Re: proposal: session server side variables