Re: Proof of concept: standalone backend with full FE/BE protocol

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, hlinnaka(at)iki(dot)fi
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol
Date: 2012-09-03 20:38:09
Message-ID: 201209032238.09694.andres@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Monday, September 03, 2012 10:23:52 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.
What I am asking myself is: why does that have to go through the normal
PQconnectdb* api? This is something completely new and very well might grow
more features that are not necessarily easy to press into PQconnectdb().

PQServer
PQstartServer(const char **keywords, const char **values);

or whatever seems to be more future proof especially considering the
possibility that this will grow into something more featureful.

Greetings,

Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-09-03 20:50:22 Re: Proof of concept: standalone backend with full FE/BE protocol
Previous Message Kohei KaiGai 2012-09-03 20:32:46 Re: [v9.3] Row-Level Security