Andrew Dunstan <and...@dunslane.net> writes: > On 09/03/2012 04:23 PM, Tom Lane wrote: >> I'm reluctantly coming to the conclusion that we can't pass these >> parameters through the regular libpq connection string mechanism, and >> will have to invent something else. That's awfully nasty though; >> it will pretty much cripple the idea that this would be a simple way to >> invoke a quasi-embedded variant of Postgres.
> That would be a bit sad. BTW, how would this work for things like > auto_vacuum, logging_collector and so on? There's already an "options" connection-string option for passing random GUC settings through to the connected backend. My original plan was to just add any such settings to the standalone backend's command line. In this context that would work for postmaster-level GUCs. However, if we're going to redesign this then maybe something else is more appropriate. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers