Re: SCRAM in the PG 10 release notes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SCRAM in the PG 10 release notes
Date: 2017-05-11 13:19:43
Message-ID: 1501.1494508783@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> I updated the List of Drivers in the Wiki. I added a few drivers that
> were missing, like the ODBC driver, and the pgtclng driver, as well as a
> Go and Rust driver that I'm aware of. I reformatted it, and added a
> column to indicate whether each driver uses libpq or not.

> https://wiki.postgresql.org/wiki/List_of_drivers

> There is a similar list in our docs:

> https://www.postgresql.org/docs/devel/static/external-interfaces.html

> Should we update the list in the docs, adding every driver we know of?
> Or curate the list somehow, adding only more popular drivers? Or perhaps
> add a link to the Wiki page from the docs?

Certainly, if that list is out of date, we need to do something about it.

ISTM that the list probably doesn't change fast enough that tracking it
in our SGML docs is a huge problem. I think it'd likely be good enough
to just add the missing drivers to the list in the docs. (If you do,
please back-patch that.)

> We can use this list in the Wiki to track which drivers implement SCRAM.

+1. That *is* something likely to change faster than we can update
the SGML docs.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-05-11 13:25:05 Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take)
Previous Message Robert Haas 2017-05-11 13:13:56 Re: Bug in pg_dump --table and --exclude-table for declarative partition table handling.