On 2013-11-20 11:08:33 -0500, Tom Lane wrote: > Andres Freund <and...@2ndquadrant.com> writes: > > On 2013-11-20 10:48:20 -0500, Tom Lane wrote: > >> constraining what can be executed as a "standalone backend". Would > >> it work to insist that psql/pg_dump launch the program named postgres > >> from the same bin directory they're in, rather than accepting a path > >> from the connection string? > > > But why do we want to start the server through the connection string > > using PQconnectb() in the first place? That doesn't really seem right to > > me. > > Something like PQstartSingleUser(dsn) returning a established connection > > seems better to me. > > That just pushes the problem up a level --- how are you going to tell > psql, pg_dump, or other programs that they should do that?
An explicit parameter. A program imo explicitly needs to be aware that a PQconnect() suddenly starts forking and such. What if it is using threads? What if it has it's own SIGCHLD handler for other business it's doing? Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
