Re: Proof of concept: standalone backend with full FE/BE protocol
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Proof of concept: standalone backend with full FE/BE protocol |
| Дата | |
| Msg-id | 528D1C45.400@gmx.net обсуждение исходный текст |
| Ответ на | 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
Re: Proof of concept: standalone backend with full FE/BE protocol |
| Список | 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 по дате отправления: