pgsql: libpq should expose GSS-related parameters even when not impleme

2019-12-20 Thread Tom Lane
libpq should expose GSS-related parameters even when not implemented. We realized years ago that it's better for libpq to accept all connection parameters syntactically, even if some are ignored or restricted due to lack of the feature in a particular build. However, that lesson from the SSL suppo

pgsql: libpq should expose GSS-related parameters even when not impleme

2019-12-20 Thread Tom Lane
libpq should expose GSS-related parameters even when not implemented. We realized years ago that it's better for libpq to accept all connection parameters syntactically, even if some are ignored or restricted due to lack of the feature in a particular build. However, that lesson from the SSL suppo

pgsql: libpq should expose GSS-related parameters even when not impleme

2019-12-20 Thread Tom Lane
libpq should expose GSS-related parameters even when not implemented. We realized years ago that it's better for libpq to accept all connection parameters syntactically, even if some are ignored or restricted due to lack of the feature in a particular build. However, that lesson from the SSL suppo

pgsql: libpq should expose GSS-related parameters even when not impleme

2019-12-20 Thread Tom Lane
libpq should expose GSS-related parameters even when not implemented. We realized years ago that it's better for libpq to accept all connection parameters syntactically, even if some are ignored or restricted due to lack of the feature in a particular build. However, that lesson from the SSL suppo

pgsql: libpq should expose GSS-related parameters even when not impleme

2019-12-20 Thread Tom Lane
libpq should expose GSS-related parameters even when not implemented. We realized years ago that it's better for libpq to accept all connection parameters syntactically, even if some are ignored or restricted due to lack of the feature in a particular build. However, that lesson from the SSL suppo

pgsql: libpq should expose GSS-related parameters even when not impleme

2019-12-20 Thread Tom Lane
libpq should expose GSS-related parameters even when not implemented. We realized years ago that it's better for libpq to accept all connection parameters syntactically, even if some are ignored or restricted due to lack of the feature in a particular build. However, that lesson from the SSL suppo

pgsql: libpq should expose GSS-related parameters even when not impleme

2019-12-20 Thread Tom Lane
libpq should expose GSS-related parameters even when not implemented. We realized years ago that it's better for libpq to accept all connection parameters syntactically, even if some are ignored or restricted due to lack of the feature in a particular build. However, that lesson from the SSL suppo