Feature request: Connection string parsing for postgres_fdw

From: Eric Hanson <eric(at)aquameta(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Feature request: Connection string parsing for postgres_fdw
Date: 2020-12-23 13:05:23
Message-ID: CACA6kxh-Vd6f-Xroi=4yBQviWANd3qxfDYDv3GMvhbr_MNgvPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'm trying to store connection to postgres_fdw in the database I want to
be able to store the full breadth of connection styles and all the
different types of connections that libpq supports. But having some
troubles.

Postgres_fdw wants options passed into CREATE SERVER, all broken out into
separate variables, but this format is neither a connection URI, nor a
keyword/value string. One could imagine writing some parser that extracts
all the variables and honors collisions in the same way libpq does (like
when both the path and the query string specify a port), but I really don't
want to recreate that.

It would be really nice if I could tap into libpq's connection string
parser from SQL and use it to extract all the variables in a given
connection string, so that I can then pipe those into CREATE SERVER
options. Either that, or teach postgres_fdw how to consume standard
connection strings.

Suggestions? Is this worthy of a feature request?

Thanks,
Eric
--
http://aquameta.org/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jammie 2020-12-23 13:35:56 Re: Movement of restart_lsn position movement of logical replication slots is very slow
Previous Message k.jamison@fujitsu.com 2020-12-23 12:57:24 RE: [Patch] Optimize dropping of relation buffers using dlist