Re: postgres_fdw hint messages - Mailing list pgsql-hackers

From Robert Haas
Subject Re: postgres_fdw hint messages
Date
Msg-id CA+TgmoY+BuSZm-Fbxx5zC6SuML=2F9YvaYuzVAJ=XyE65BnchQ@mail.gmail.com
Whole thread Raw
In response to postgres_fdw hint messages  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: postgres_fdw hint messages
List pgsql-hackers
On Thu, Aug 25, 2022 at 9:42 AM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
> The postgres_fdw tests contain this (as amended by patch 0001):
>
> ALTER SERVER loopback_nopw OPTIONS (ADD password 'dummypw');
> ERROR:  invalid option "password"
> HINT:  Valid options in this context are: service, passfile,
> channel_binding, connect_timeout, dbname, host, hostaddr, port, options,
> application_name, keepalives, keepalives_idle, keepalives_interval,
> keepalives_count, tcp_user_timeout, sslmode, sslcompression, sslcert,
> sslkey, sslrootcert, sslcrl, sslcrldir, sslsni, requirepeer,
> ssl_min_protocol_version, ssl_max_protocol_version, gssencmode,
> krbsrvname, gsslib, target_session_attrs, use_remote_estimate,
> fdw_startup_cost, fdw_tuple_cost, extensions, updatable, truncatable,
> fetch_size, batch_size, async_capable, parallel_commit, keep_connections
>
> This annoys developers who are working on libpq connection options,
> because any option added, removed, or changed causes this test to need
> to be updated.
>
> It's also questionable how useful this hint is in its current form,
> considering how long it is and that the options are in an
> implementation-dependent order.

I think the place to list the legal options is in the documentation,
not the HINT.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: configure --with-uuid=bsd fails on NetBSD
Next
From: Robert Haas
Date:
Subject: Re: Letter case of "admin option"