From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Jacob Champion <pchampion(at)vmware(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "hlinnaka(at)iki(dot)fi" <hlinnaka(at)iki(dot)fi>, "andrew(dot)dunstan(at)2ndquadrant(dot)com" <andrew(dot)dunstan(at)2ndquadrant(dot)com>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>, "thomas(dot)munro(at)gmail(dot)com" <thomas(dot)munro(at)gmail(dot)com> |
Subject: | Re: Support for NSS as a libpq TLS backend |
Date: | 2022-02-04 20:03:50 |
Message-ID: | 20220204200350.GG10577@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Daniel Gustafsson (daniel(at)yesql(dot)se) wrote:
> I am writing done above in quotes, since the documentation also needs to be
> updated, completed, rewritten, organized etc etc. The above is an import of
> what was found, and is in a fairly poor state. Unfortunately, it's still not
> in the tree where I personally believe documentation stands the best chance of
> being kept up to date. The NSPR documentation is probably the best of the two,
> but it's also much less of a moving target.
I wonder about the 'not in tree' bit since it is in the header files,
certainly for NSPR which I've been poking at due to this discussion. I
had hoped that they were generating the documentation on the webpage
from what's in the header files, is that not the case then? Which is
more accurate? If it's a simple matter of spending time going through
what's in the tree and making sure what's online matches that, I suspect
we could find some folks with time to work on helping them there.
If the in-tree stuff isn't accurate then that's a bigger problem, of
course.
> It is true that the documentation is poor and currently in bad shape with lots
> of broken links and heavily disorganized etc. It's also true that I managed to
> implement full libpq support without any crystal ball or help from the NSS
> folks. The latter doesn't mean we can brush documentation concerns aside, but
> let's be fair in our criticism.
Agreed.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2022-02-04 20:05:06 | Re: should vacuum's first heap pass be read-only? |
Previous Message | Stephen Frost | 2022-02-04 19:59:35 | Re: Support for NSS as a libpq TLS backend |