Re: Proof of concept: standalone backend with full FE/BE protocol - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Proof of concept: standalone backend with full FE/BE protocol
Date
Msg-id CA+U5nM+zO+=O0jbRPTu2M4WkVV4NMv2Zjr2GpBt1vnBqteTjoA@mail.gmail.com
Whole thread Raw
In response to Re: Proof of concept: standalone backend with full FE/BE protocol  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Proof of concept: standalone backend with full FE/BE protocol
List pgsql-hackers
On 5 December 2013 01:55, Peter Eisentraut <peter_e@gmx.net> wrote:
> On Thu, 2013-11-14 at 12:11 +0530, Amit Kapila wrote:
>>    If an application wants to allow these connection parameters to be
>> used, it would need to do PQenableStartServer() first. If it doesn't,
>> those connection parameters will be rejected.
>
> Stupid idea: Would it work that we require an environment variable to be
> set before we allow the standalone_backend connection parameter?  That's
> easy to do, easy to audit, and doesn't require any extra code in the
> individual clients.

I like the idea... should it be in pg_hba.conf ?
Or should it be next to listen_addresses in postgresql.conf?

hba might be less convenient but seems like the correct place

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Proposal: variant of regclass
Next
From: Andres Freund
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol