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

From Peter Eisentraut
Subject Re: Proof of concept: standalone backend with full FE/BE protocol
Date
Msg-id 528D1C45.400@gmx.net
Whole thread Raw
In response to Re: Proof of concept: standalone backend with full FE/BE protocol  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Proof of concept: standalone backend with full FE/BE protocol  (Robert Haas <robertmhaas@gmail.com>)
Re: Proof of concept: standalone backend with full FE/BE protocol  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 11/20/13, 3:24 PM, Robert Haas wrote:
> The point is that client applications should expose whether or not to
> set this function as a command-line switch separate from whatever they
> accept in terms of connection strings.  So pg_dump should have a flag
> called --standalone-server or something like, and it should all
> PQenableStartServer() only when that flag is used.

The argument elsewhere in this thread was that the reason for putting
this in the connection options was so that you do *not* have to patch up
every client to be able to use this functionality.  If you have to add
separate options everywhere, then you might as well just have a separate
libpq function to initiate the session.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol
Next
From: Robert Haas
Date:
Subject: Re: Easily reading debug_print_plan