Feature request: Connection string parsing for postgres_fdw

Поиск
Список
Период
Сортировка
От Eric Hanson
Тема Feature request: Connection string parsing for postgres_fdw
Дата
Msg-id CACA6kxh-Vd6f-Xroi=4yBQviWANd3qxfDYDv3GMvhbr_MNgvPg@mail.gmail.com
обсуждение исходный текст
Ответы Re: Feature request: Connection string parsing for postgres_fdw  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Re: Feature request: Connection string parsing for postgres_fdw  (Ian Lawrence Barwick <barwick@gmail.com>)
Список 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?

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "k.jamison@fujitsu.com"
Дата:
Сообщение: RE: [Patch] Optimize dropping of relation buffers using dlist
Следующее
От: Jammie
Дата:
Сообщение: Re: Movement of restart_lsn position movement of logical replication slots is very slow