Re: Proof of concept: standalone backend with full FE/BE protocol
| От | Tom Lane |
|---|---|
| Тема | Re: Proof of concept: standalone backend with full FE/BE protocol |
| Дата | |
| Msg-id | 20852.1385045098@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Proof of concept: standalone backend with full FE/BE protocol (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
Re: Proof of concept: standalone backend with full FE/BE protocol
|
| Список | pgsql-hackers |
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? That seems bizarre. If we're going to use a special switch
to enable standalone mode, it should be the same on every program
that supports it.
regards, tom lane
В списке pgsql-hackers по дате отправления: