Re: Proof of concept: standalone backend with full FE/BE protocol

On Thu, Nov 21, 2013 at 8:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Amit Kapila <amit.kapila16@gmail.com> writes:
>> Here what I have in mind is that:
>> a. In pg_dump or other internal utilities where we want to use this
>> feature, they should call PQenableStart()  or some other API before
>>     calling PQConnect() which will indicate that it wants to operate
>> as a standalone mode.
>> b. In psql, if user specifies this special switch (
>> 'standalone_datadir'), then internally we will call PQenableStart()
>> and use postgres from same
>>     directory.
>
> Why would you make psql behave differently from our other command-line
> clients?
  No, psql should not behave different from other clients. Sorry, I
was under assumption that for other programs we will not take backend
executable  path.  One other thing which is not clear to me is that how by calling
some special/new API we can ensure that the path provided by user is  a valid path, are we going to validate file given
in
'standalone_backend'  switch in some way?


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com