| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, simon(at)2ndQuadrant(dot)com, Merlin Moncure <mmoncure(at)gmail(dot)com>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proof of concept: standalone backend with full FE/BE protocol |
| Date: | 2013-12-05 16:39:29 |
| Message-ID: | 52A0AC41.2080706@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I think this proposal is a bit deadlocked now.
- There are technical concerns about launching a server executable from
within a client.
- There are conceptual concerns about promoting an embedded database mode.
On the other hand:
- Everyone would like to have a way to use psql (and other basic
clients) in stand-alone mode.
The compromise would be to not launch the server from within the client,
but have client and server communicate over external mechanisms (e.g.,
Unix-domain socket).
The concern about that was that it would open up standalone mode to
accidental third-party connections. While there are some ways around
that (socket in private directory), they are not easy and not portable.
So standalone mode would became less robust and reliable overall.
The only solutions I see are:
1. do nothing
2. do everything (i.e., existing terminal mode plus socket mode plus
embedded mode), letting the user work out the differences
Pick one. ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-12-05 16:45:51 | Re: logical changeset generation v6.7 |
| Previous Message | David Johnston | 2013-12-05 16:37:39 | Re: [RFC] Shouldn't we remove annoying FATAL messages from server log? |