Thread

Commits

  1. Fix conversion table generator scripts.

  2. doc: Refresh more URLs in the docs

  3. Doc: update or remove dead external links.

  4. Rewrite the perl scripts to produce our Unicode conversion tables.

  1. Stale external URL in doc?

    Kyotaro Horiguchi <horikyota.ntt@gmail.com> — 2020-07-09T07:12:26Z

    Hello.
    
    I see the following description in the doc.
    
    https://www.postgresql.org/docs/13/ssl-tcp.html
    
    Intermediate certificates that chain up to existing root certificates
    can also appear in the ssl_ca_file file if you wish to avoid storing
    them on clients (assuming the root and intermediate certificates were
    created with v3_ca extensions). Certificate Revocation List (CRL)
    entries are also checked if the parameter ssl_crl_file is set. (See
    http://h41379.www4.hpe.com/doc/83final/ba554_90007/ch04s02.html for
    diagrams showing SSL certificate usage.)
    
    I follwed the URL above and saw the "Support and other resources" page
    of the document "OpeNVMS Systems Documemtation Index page".
    
    FWIW the folloing URL shows "HP Open Source Security for OpenVMS
    Volume 2: HP SSL for Open VMS", which seems to be the originally
    intended document..
    
    https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04622320
    
    regards.
    
    -- 
    Kyotaro Horiguchi
    NTT Open Source Software Center
    
    
    
    
    
    
  2. Re: Stale external URL in doc?

    Daniel Gustafsson <daniel@yesql.se> — 2020-07-09T07:46:44Z

    > On 9 Jul 2020, at 09:12, Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote:
    > 
    > Hello.
    > 
    > I see the following description in the doc.
    > 
    > https://www.postgresql.org/docs/13/ssl-tcp.html
    > 
    > Intermediate certificates that chain up to existing root certificates
    > can also appear in the ssl_ca_file file if you wish to avoid storing
    > them on clients (assuming the root and intermediate certificates were
    > created with v3_ca extensions). Certificate Revocation List (CRL)
    > entries are also checked if the parameter ssl_crl_file is set. (See
    > http://h41379.www4.hpe.com/doc/83final/ba554_90007/ch04s02.html for
    > diagrams showing SSL certificate usage.)
    > 
    > I follwed the URL above and saw the "Support and other resources" page
    > of the document "OpeNVMS Systems Documemtation Index page".
    
    Right, it's redirecting there now. The same goes for a link to hpe.com on
    https://www.postgresql.org/docs/13/libpq-ssl.html which too is redirected
    to a larger documentation set.
    
    > FWIW the folloing URL shows "HP Open Source Security for OpenVMS
    > Volume 2: HP SSL for Open VMS", which seems to be the originally
    > intended document..
    > 
    > https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04622320
    
    The intended document is a page which is more concise and to the point, the
    full OpenVMS SSL documentation set doesn't really fit the purpose for this
    link.
    
    As a short term fix we should either a) remove these links completely or b)
    link to archived copies of the pages on archive.org; or c) find a more
    appropriate pages to link to.  A quick search didn't turn up anything I would
    prefer for (c), and I'm not sure what he legality of linking to a cached copy
    is, so I would advocate for (a).
    
    Longer term we should try to incorporate (some of) these diagrams and content
    into our own documentation now that we have proper capability for inline
    images.
    
    cheers ./daniel
    
    
    
    
  3. Re: Stale external URL in doc?

    Tom Lane <tgl@sss.pgh.pa.us> — 2020-07-09T13:51:51Z

    Daniel Gustafsson <daniel@yesql.se> writes:
    > As a short term fix we should either a) remove these links completely or b)
    > link to archived copies of the pages on archive.org; or c) find a more
    > appropriate pages to link to.  A quick search didn't turn up anything I would
    > prefer for (c), and I'm not sure what he legality of linking to a cached copy
    > is, so I would advocate for (a).
    
    +1.  It should have been obvious just from the spelling of this URL that
    it wasn't intended to be a long term stable location.  Digging in the
    git history shows we've already updated it twice, and I wonder how many
    changes there were that we didn't notice.
    
    Just reverting bbd3bdba3 seems appropriate to me.
    
    			regards, tom lane
    
    
    
    
  4. Re: Stale external URL in doc?

    Magnus Hagander <magnus@hagander.net> — 2020-07-09T15:54:53Z

    On Thu, Jul 9, 2020 at 3:52 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
    
    > Daniel Gustafsson <daniel@yesql.se> writes:
    > > As a short term fix we should either a) remove these links completely or
    > b)
    > > link to archived copies of the pages on archive.org; or c) find a more
    > > appropriate pages to link to.  A quick search didn't turn up anything I
    > would
    > > prefer for (c), and I'm not sure what he legality of linking to a cached
    > copy
    > > is, so I would advocate for (a).
    >
    > +1.  It should have been obvious just from the spelling of this URL that
    > it wasn't intended to be a long term stable location.  Digging in the
    > git history shows we've already updated it twice, and I wonder how many
    > changes there were that we didn't notice.
    >
    > Just reverting bbd3bdba3 seems appropriate to me.
    >
    
    +1.
    
    If we want to keep a set of such links, probably the wiki is a better place
    as more people can easily fix them there.
    
    -- 
     Magnus Hagander
     Me: https://www.hagander.net/ <http://www.hagander.net/>
     Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
    
  5. Re: Stale external URL in doc?

    Alvaro Herrera <alvherre@2ndquadrant.com> — 2020-07-09T16:36:43Z

    On 2020-Jul-09, Magnus Hagander wrote:
    
    > If we want to keep a set of such links, probably the wiki is a better place
    > as more people can easily fix them there.
    
    Or, since our docs have diagram capabilities now, we can make our own
    diagram.
    
    -- 
    Álvaro Herrera                https://www.2ndQuadrant.com/
    PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
    
    
    
    
  6. Re: Stale external URL in doc?

    Magnus Hagander <magnus@hagander.net> — 2020-07-09T18:03:50Z

    On Thu, Jul 9, 2020 at 6:36 PM Alvaro Herrera <alvherre@2ndquadrant.com>
    wrote:
    
    > On 2020-Jul-09, Magnus Hagander wrote:
    >
    > > If we want to keep a set of such links, probably the wiki is a better
    > place
    > > as more people can easily fix them there.
    >
    > Or, since our docs have diagram capabilities now, we can make our own
    > diagram.
    >
    
    Absolutely. I meant more as a general thing if we want to refer to websites
    outside of our control for other things.
    
    -- 
     Magnus Hagander
     Me: https://www.hagander.net/ <http://www.hagander.net/>
     Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
    
  7. Re: Stale external URL in doc?

    Daniel Gustafsson <daniel@yesql.se> — 2020-07-09T22:06:42Z

    > On 9 Jul 2020, at 17:54, Magnus Hagander <magnus@hagander.net> wrote:
    > 
    > On Thu, Jul 9, 2020 at 3:52 PM Tom Lane <tgl@sss.pgh.pa.us <mailto:tgl@sss.pgh.pa.us>> wrote:
    > Daniel Gustafsson <daniel@yesql.se <mailto:daniel@yesql.se>> writes:
    > > As a short term fix we should either a) remove these links completely or b)
    > > link to archived copies of the pages on archive.org <http://archive.org/>; or c) find a more
    > > appropriate pages to link to.  A quick search didn't turn up anything I would
    > > prefer for (c), and I'm not sure what he legality of linking to a cached copy
    > > is, so I would advocate for (a).
    > 
    > +1.  It should have been obvious just from the spelling of this URL that
    > it wasn't intended to be a long term stable location.  Digging in the
    > git history shows we've already updated it twice, and I wonder how many
    > changes there were that we didn't notice.
    > 
    > Just reverting bbd3bdba3 seems appropriate to me.
    > 
    > +1.
    > 
    > If we want to keep a set of such links, probably the wiki is a better place as more people can easily fix them there.
    
    Taking a look at other links to external resources, most links seemed to
    resolve still (but I didn't test all of them).  I did find another one on the
    GEQO page which is now dead without the content available elsewhere, as well as
    a larger problem with the AIX references.
    
    We have a list of links to the AIX 6.1 documentation which no longer works as
    IBM only provides docset PDFs for 6.1.  Looking that 7.x documentation they
    have reorganized enough to make the older links not directly translatable.  I
    do wonder if updating this list is worth the effort, or if it will only lead to
    us revisiting this once IBM does another site change.
    
    The attached suggestion removes the reported SSL links, the FAQ linked to on
    GEQO and all the IBM links, fully realizing that it might be controversial to
    some extent.
    
    cheers ./daniel
    
    
  8. Re: Stale external URL in doc?

    Tom Lane <tgl@sss.pgh.pa.us> — 2020-07-09T22:51:18Z

    Daniel Gustafsson <daniel@yesql.se> writes:
    > Taking a look at other links to external resources, most links seemed to
    > resolve still (but I didn't test all of them).  I did find another one on the
    > GEQO page which is now dead without the content available elsewhere, as well as
    > a larger problem with the AIX references.
    
    > We have a list of links to the AIX 6.1 documentation which no longer works as
    > IBM only provides docset PDFs for 6.1.  Looking that 7.x documentation they
    > have reorganized enough to make the older links not directly translatable.  I
    > do wonder if updating this list is worth the effort, or if it will only lead to
    > us revisiting this once IBM does another site change.
    
    > The attached suggestion removes the reported SSL links, the FAQ linked to on
    > GEQO and all the IBM links, fully realizing that it might be controversial to
    > some extent.
    
    +1 for just deleting all of it.  I don't think we need to be telling users
    of obsolete AIX versions how to run their systems.  The comp.ai.genetic
    FAQ link might be more of a loss, but on the other hand I'd be willing to
    bet it wasn't very up to date anymore.  Netnews has been moribund for a
    long time :-(
    
    			regards, tom lane
    
    
    
    
  9. Re: Stale external URL in doc?

    Alvaro Herrera <alvherre@2ndquadrant.com> — 2020-07-10T00:08:38Z

    On 2020-Jul-10, Daniel Gustafsson wrote:
    
    > Taking a look at other links to external resources, most links seemed to
    > resolve still (but I didn't test all of them).  I did find another one on the
    > GEQO page which is now dead without the content available elsewhere, as well as
    > a larger problem with the AIX references.
    
    Um, the comp.ai.genetic FAQ can still be found, eg. 
    http://www.faqs.org/faqs/ai-faq/genetic/part1/
    
    
    
    -- 
    Álvaro Herrera                https://www.2ndQuadrant.com/
    PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
    
    
    
    
  10. Re: Stale external URL in doc?

    Tom Lane <tgl@sss.pgh.pa.us> — 2020-07-10T16:28:17Z

    Alvaro Herrera <alvherre@2ndquadrant.com> writes:
    > On 2020-Jul-10, Daniel Gustafsson wrote:
    >> Taking a look at other links to external resources, most links seemed to
    >> resolve still (but I didn't test all of them).  I did find another one on the
    >> GEQO page which is now dead without the content available elsewhere, as well as
    >> a larger problem with the AIX references.
    
    > Um, the comp.ai.genetic FAQ can still be found, eg. 
    > http://www.faqs.org/faqs/ai-faq/genetic/part1/
    
    So it is, although that also shows it hasn't been updated since 2001.
    
    OTOH, that vintage of info is probably just fine for understanding GEQO.
    
    I'll go update that pointer and remove the other links per Daniel's
    patch.
    
    			regards, tom lane
    
    
    
    
  11. Re: Stale external URL in doc?

    Daniel Gustafsson <daniel@yesql.se> — 2020-07-10T21:41:38Z

    > On 10 Jul 2020, at 18:28, Tom Lane <tgl@sss.pgh.pa.us> wrote:
    > Alvaro Herrera <alvherre@2ndquadrant.com> writes:
    
    >> Um, the comp.ai.genetic FAQ can still be found, eg. 
    >> http://www.faqs.org/faqs/ai-faq/genetic/part1/
    > 
    > So it is, although that also shows it hasn't been updated since 2001.
    
    Ah, I missed the alternative source.
    
    > I'll go update that pointer and remove the other links per Daniel's
    > patch.
    
    Thanks for the fixup.
    
    cheers ./daniel
    
    
    
    
  12. Re: Stale external URL in doc?

    Thomas Munro <thomas.munro@gmail.com> — 2020-07-10T21:42:17Z

    On Fri, Jul 10, 2020 at 10:07 AM Daniel Gustafsson <daniel@yesql.se> wrote:
    > (but I didn't test all of them)
    
    Cave-person shell script time:
    
    for url in ` git grep 'url="http' | sed 's/.*url="//;s/".*//' | sort | uniq `
    do
      if ! curl --output /dev/null --silent --head --fail "$url"
      then
        echo "bad URL: $url"
      fi
    done
    
    bad URL: https://mingw-w64.org/
    bad URL: https://msdn.microsoft.com/en-us/library/aa380493%28VS.85%29.aspx
    bad URL: https://ssl.icu-project.org/icu-bin/locexp
    bad URL: https://www.ismn-international.org/ranges.html
    
    The Microsoft one is OK, it's a redirect, but the redirect target
    looks like a more permanent URL to me so maybe we should change it.
    The others required minor manual sleuthing to correct; I hope I found
    the correct ISN ranges page.  Please see attached.
    
    Looking at the ICU URL, I found a couple like that in our source tree,
    and fixed those too, including one used by
    src/backend/utils/mb/Unicode/Makefile to fetch source data which has
    moved (http://site.icu-project.org/repository says "Announcement
    07/16/2018: The ICU source code repository has been migrated from
    Subversion to Git, and is now hosted on GitHub.").
    
  13. Re: Stale external URL in doc?

    Tom Lane <tgl@sss.pgh.pa.us> — 2020-07-10T21:47:38Z

    Thomas Munro <thomas.munro@gmail.com> writes:
    > The Microsoft one is OK, it's a redirect, but the redirect target
    > looks like a more permanent URL to me so maybe we should change it.
    
    +1
    
    > The others required minor manual sleuthing to correct; I hope I found
    > the correct ISN ranges page.  Please see attached.
    
    I didn't actually check any of these, but they look like sane changes.
    
    			regards, tom lane
    
    
    
    
  14. Re: Stale external URL in doc?

    Daniel Gustafsson <daniel@yesql.se> — 2020-07-10T21:55:59Z

    > On 10 Jul 2020, at 23:47, Tom Lane <tgl@sss.pgh.pa.us> wrote:
    > Thomas Munro <thomas.munro@gmail.com> writes:
    
    >> The others required minor manual sleuthing to correct; I hope I found
    >> the correct ISN ranges page.  Please see attached.
    > 
    > I didn't actually check any of these, but they look like sane changes.
    
    +1, looks good, thanks!
    
    cheers ./daniel
    
    
    
    
  15. Re: Stale external URL in doc?

    Thomas Munro <thomas.munro@gmail.com> — 2020-07-11T03:25:54Z

    On Sat, Jul 11, 2020 at 9:56 AM Daniel Gustafsson <daniel@yesql.se> wrote:
    > > On 10 Jul 2020, at 23:47, Tom Lane <tgl@sss.pgh.pa.us> wrote:
    > > Thomas Munro <thomas.munro@gmail.com> writes:
    > >> The others required minor manual sleuthing to correct; I hope I found
    > >> the correct ISN ranges page.  Please see attached.
    > >
    > > I didn't actually check any of these, but they look like sane changes.
    >
    > +1, looks good, thanks!
    
    Is it OK that I see the following warning many times when running
    "make" under src/backend/utils/mb/Unicode?  It looks like this code is
    from commit 1de9cc0d.  Horiguchi-san, do you think something changed
    (input data format, etc) since you wrote it, or maybe some later
    changes just made our perl scripts more picky about warnings?
    
      Use of uninitialized value $val in printf at convutils.pm line 612.
    
    
    
    
  16. Re: Stale external URL in doc?

    Daniel Gustafsson <daniel@yesql.se> — 2020-07-13T09:36:17Z

    > On 11 Jul 2020, at 05:25, Thomas Munro <thomas.munro@gmail.com> wrote:
    
    > Is it OK that I see the following warning many times when running
    > "make" under src/backend/utils/mb/Unicode?  It looks like this code is
    > from commit 1de9cc0d.  Horiguchi-san, do you think something changed
    > (input data format, etc) since you wrote it, or maybe some later
    > changes just made our perl scripts more picky about warnings?
    > 
    >  Use of uninitialized value $val in printf at convutils.pm line 612.
    
    Confirmed here as well, combined with the below ones for a few of the files:
    
    Use of uninitialized value in hash element at convutils.pm line 448.
    Use of uninitialized value $b1root in printf at convutils.pm line 558.
    Use of uninitialized value $b1_lower in printf at convutils.pm line 560.
    Use of uninitialized value $b1_upper in printf at convutils.pm line 561.
    Use of uninitialized value $b3root in printf at convutils.pm line 570.
    Use of uninitialized value $b3_1_lower in printf at convutils.pm line 572.
    Use of uninitialized value $b3_1_upper in printf at convutils.pm line 573.
    Use of uninitialized value $b3_2_lower in printf at convutils.pm line 574.
    Use of uninitialized value $b3_2_upper in printf at convutils.pm line 575.
    Use of uninitialized value $b3_3_lower in printf at convutils.pm line 576.
    Use of uninitialized value $b3_3_upper in printf at convutils.pm line 577.
    Use of uninitialized value $val in printf at convutils.pm line 612.
    
    cheers ./daniel
    
    
    
    
  17. Re: Stale external URL in doc?

    Kyotaro Horiguchi <horikyota.ntt@gmail.com> — 2020-07-14T00:00:11Z

    At Mon, 13 Jul 2020 11:36:17 +0200, Daniel Gustafsson <daniel@yesql.se> wrote in 
    > > On 11 Jul 2020, at 05:25, Thomas Munro <thomas.munro@gmail.com> wrote:
    > 
    > > Is it OK that I see the following warning many times when running
    > > "make" under src/backend/utils/mb/Unicode?  It looks like this code is
    > > from commit 1de9cc0d.  Horiguchi-san, do you think something changed
    > > (input data format, etc) since you wrote it, or maybe some later
    > > changes just made our perl scripts more picky about warnings?
    > > 
    > >  Use of uninitialized value $val in printf at convutils.pm line 612.
    > 
    > Confirmed here as well, combined with the below ones for a few of the files:
    > 
    > Use of uninitialized value in hash element at convutils.pm line 448.
    > Use of uninitialized value $b1root in printf at convutils.pm line 558.
    > Use of uninitialized value $b1_lower in printf at convutils.pm line 560.
    
    Mmm. I see the same, too. I'm looking into that.
    
    regards.
    
    -- 
    Kyotaro Horiguchi
    NTT Open Source Software Center
    
    
    
    
  18. Re: Stale external URL in doc?

    Kyotaro Horiguchi <horikyota.ntt@gmail.com> — 2020-07-14T03:26:56Z

    It is found to be a time capsule full of worms..
    
    At Tue, 14 Jul 2020 09:00:11 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in 
    > > Use of uninitialized value $b1_lower in printf at convutils.pm line 560.
    > 
    > Mmm. I see the same, too. I'm looking into that.
    
    There are three easy-to-fix issues:
    
    1. The script set utilized undef as zeros, so most of them are fixed
      by using zero for undefs.
    
    2. Some Japanese-related converter scripts seem to be affected by a
      change of regexp greediness and easily fixed.
    
    3. I got a certificate error for ssl.icu-project.org and found that
      the name is changed to icu-project.org. 
    
    And one issue that I'm not sure how we shold treat this:
    
    A. I didn't find the files gb-18030-2000.xml and windows-949-2000.xml
      in the ICU site.  We have our own copy in our repository so it's not
      a serious problem but I'm not sure what we should do for this.
    
      I found CP949.TXT for windows-949-2000.xml but the former is missing
      mappings for certaion code ranges (c9xx and fexx).
    
    
    The attached is the fix for 1 to 3 above. It doesn't contain changes
    in .map files.
    
    regards.
    
    -- 
    Kyotaro Horiguchi
    NTT Open Source Software Center
    
  19. Re: Stale external URL in doc?

    Thomas Munro <thomas.munro@gmail.com> — 2020-07-14T03:40:41Z

    On Tue, Jul 14, 2020 at 3:27 PM Kyotaro Horiguchi
    <horikyota.ntt@gmail.com> wrote:
    > A. I didn't find the files gb-18030-2000.xml and windows-949-2000.xml
    >   in the ICU site.  We have our own copy in our repository so it's not
    >   a serious problem but I'm not sure what we should do for this.
    
    The patch I posted earlier fixes that problem (their source repository moved).
    
    
    
    
  20. Re: Stale external URL in doc?

    Kyotaro Horiguchi <horikyota.ntt@gmail.com> — 2020-07-14T05:03:32Z

    At Tue, 14 Jul 2020 15:40:41 +1200, Thomas Munro <thomas.munro@gmail.com> wrote in 
    > On Tue, Jul 14, 2020 at 3:27 PM Kyotaro Horiguchi
    > <horikyota.ntt@gmail.com> wrote:
    > > A. I didn't find the files gb-18030-2000.xml and windows-949-2000.xml
    > >   in the ICU site.  We have our own copy in our repository so it's not
    > >   a serious problem but I'm not sure what we should do for this.
    > 
    > The patch I posted earlier fixes that problem (their source repository moved).
    
    - $(DOWNLOAD) https://ssl.icu-project.org/repos/icu/data/trunk/charset/data/xml/$(@F)
    + $(DOWNLOAD) https://raw.githubusercontent.com/unicode-org/icu-data/master/charset/data/xml/$(@F)
    
    Wow. The URL works and makes no difference in related map files.
    
    Thanks!
    
    -- 
    Kyotaro Horiguchi
    NTT Open Source Software Center
    
    
    
    
  21. Re: Stale external URL in doc?

    Daniel Gustafsson <daniel@yesql.se> — 2020-07-16T12:09:17Z

    > On 10 Jul 2020, at 23:55, Daniel Gustafsson <daniel@yesql.se> wrote:
    > 
    >> On 10 Jul 2020, at 23:47, Tom Lane <tgl@sss.pgh.pa.us> wrote:
    >> Thomas Munro <thomas.munro@gmail.com> writes:
    > 
    >>> The others required minor manual sleuthing to correct; I hope I found
    >>> the correct ISN ranges page.  Please see attached.
    >> 
    >> I didn't actually check any of these, but they look like sane changes.
    > 
    > +1, looks good, thanks!
    
    Since this is still in flight, I'm tacking on a few more in the attached diff
    that I stumbled across.  gnu.org will redirect from http to https so we might
    as well have that in our docs from the start.
    
    cheers ./daniel
    
    
  22. Re: Stale external URL in doc?

    Kyotaro Horiguchi <horikyota.ntt@gmail.com> — 2020-07-17T03:13:08Z

    At Thu, 16 Jul 2020 14:09:17 +0200, Daniel Gustafsson <daniel@yesql.se> wrote in 
    > > On 10 Jul 2020, at 23:55, Daniel Gustafsson <daniel@yesql.se> wrote:
    > > 
    > >> On 10 Jul 2020, at 23:47, Tom Lane <tgl@sss.pgh.pa.us> wrote:
    > >> Thomas Munro <thomas.munro@gmail.com> writes:
    > > 
    > >>> The others required minor manual sleuthing to correct; I hope I found
    > >>> the correct ISN ranges page.  Please see attached.
    > >> 
    > >> I didn't actually check any of these, but they look like sane changes.
    > > 
    > > +1, looks good, thanks!
    > 
    > Since this is still in flight, I'm tacking on a few more in the attached diff
    > that I stumbled across.  gnu.org will redirect from http to https so we might
    > as well have that in our docs from the start.
    
    I checked through http:// URLs in the documentation.
    
    1. 505 Not found (0001-Fix-505-URL.patch)
    
      (Shows login page instead)  
      http://citeseer.ist.psu.edu/seshadri95generalized.html 
        => https://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.40.5740
    
    2. moved or rearranged (0002-Fixed-URLs-mofed-or-rearranged.patch)
    
      http://initd.org/psycopg/
        => https://www.psycopg.org/
    
      http://db.cs.berkeley.edu => https://dsf.berkeley.edu
        http://db.cs.berkeley.edu/jmh/
        http://db.cs.berkeley.edu/papers/
        http://db.cs.berkeley.edu/papers/ERL-M85-95.pdf
        http://db.cs.berkeley.edu/papers/ERL-M87-06.pdf
        http://db.cs.berkeley.edu/papers/ERL-M87-13.pdf
        http://db.cs.berkeley.edu/papers/ERL-M89-17.pdf
        http://db.cs.berkeley.edu/papers/ERL-M89-82.pdf
        http://db.cs.berkeley.edu/papers/ERL-M90-34.pdf
        http://db.cs.berkeley.edu/papers/ERL-M90-36.pdf
        http://db.cs.berkeley.edu/papers/UCB-MS-zfong.pdf
        http://db.cs.berkeley.edu/postgres.html
    
       (I counldn't find the eqquivalent for http://gist.cs.berkeley.edu/
        in dsf.berkeley.edu)
    
       http://json.org =>  https://www.json.org  (Redirects to localized page)
    
    
    3. Has the same page for https://  (0003-change-http-URLs-to-https.patch)
      http://cve.mitre.org/
      http://jlcooke.ca/random/
      http://postgis.net/
      http://pqxx.org/
      http://pubs.opengroup.org/onlinepubs/009695399/functions/strftime.html
      http://snowballstem.org/
      http://sourceware.org/systemtap/
      http://standards.ieee.org/
      http://standards.iso.org/ittf/PubliclyAvailableStandards/c067367_ISO_IEC_TR_19075-6_2017.zip
      http://web.mit.edu/Kerberos/dist/index.html
      http://www.issn.org/
      http://www.iusmentis.com/security/passphrasefaq/
      http://www.loc.gov/standards/iso639-2/php/English_list.php
      http://www.npgsql.org/
      http://www.openwall.com/crypt/
      http://www.perl.org
      http://www.red3d.com/cwr/evolve.html
      http://www.slony.info
      http://www.tcl.tk/
      http://www.zlib.net
      http://zlatkovic.com/pub/libxml
      (http://www.gnu.org/software/gettext/)
      (http://www.gnu.org/software/libtool/)
    
    4. Has https:// page with some troubles.
      http://www.sunfreeware.com  (insecure certificate)
      http://xmlsoft.org (insercure certificate)
       http://xmlsoft.org/
       http://xmlsoft.org/XSLT/
      http://www.tpc.org/ (private certificate and ... looks odd..)
    
    
    5. Seems not having https pages.
      http://gist.cs.berkeley.edu/
      http://gnuwin32.sourceforge.net
      http://newbiedoc.sourceforge.net/metadoc/docbook-guide.html
      http://meteora.ucsd.edu/s2k/s2k_home.html
      http://sg.danny.cz/sg/sdparm.html
      http://userguide.icu-project.org/collation/api
      http://userguide.icu-project.org/locale
      http://world.std.com/~reinhold/diceware.html
      http://www.faqs.org/faqs/ai-faq/genetic/part1/
      http://www.interhack.net/people/cmcurtin/snake-oil-faq.html
      http://www.mingw.org/
      http://www.mingw.org/wiki/MSYS
      http://www.ossp.org/pkg/lib/uuid/
      http://www.sai.msu.su/~megera/oddmuse/index.cgi/Gin
      http://www.sai.msu.su/~megera/postgres/gist/
      http://www.sai.msu.su/~megera/postgres/gist/papers/concurrency/access-methods-for-next-generation.pdf.gz
      http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/
      http://www.sai.msu.su/~megera/wiki/Gin
      http://www.sai.msu.su/~megera/wiki/spgist_dev
      http://xahlee.info/UnixResource_dir/_/ldpath.html
    
    I attached fixes for 1, 2 and 3, and not for 4. (5 doesn't need
    changes).
    
    regards.
    
    -- 
    Kyotaro Horiguchi
    NTT Open Source Software Center
    
  23. Re: Stale external URL in doc?

    Michael Paquier <michael@paquier.xyz> — 2020-07-17T05:03:18Z

    On Fri, Jul 17, 2020 at 12:13:08PM +0900, Kyotaro Horiguchi wrote:
    > I checked through http:// URLs in the documentation.
    
    It would be better to get all that fixed and backpatched. Is somebody
    already looking into that?
    --
    Michael
    
  24. Re: Stale external URL in doc?

    Michael Paquier <michael@paquier.xyz> — 2020-07-18T13:48:47Z

    On Fri, Jul 17, 2020 at 02:03:18PM +0900, Michael Paquier wrote:
    > It would be better to get all that fixed and backpatched. Is somebody
    > already looking into that?
    
    I have been through this set, and applied the changes as of 045d03f & 
    friends.  There was an extra URL broken in 9.5 and 9.6 related to the
    passphrase FAQ.
    --
    Michael
    
  25. Re: Stale external URL in doc?

    Bruce Momjian <bruce@momjian.us> — 2020-07-20T19:39:50Z

    On Thu, Jul  9, 2020 at 09:51:51AM -0400, Tom Lane wrote:
    > Daniel Gustafsson <daniel@yesql.se> writes:
    > > As a short term fix we should either a) remove these links completely or b)
    > > link to archived copies of the pages on archive.org; or c) find a more
    > > appropriate pages to link to.  A quick search didn't turn up anything I would
    > > prefer for (c), and I'm not sure what he legality of linking to a cached copy
    > > is, so I would advocate for (a).
    > 
    > +1.  It should have been obvious just from the spelling of this URL that
    > it wasn't intended to be a long term stable location.  Digging in the
    > git history shows we've already updated it twice, and I wonder how many
    > changes there were that we didn't notice.
    > 
    > Just reverting bbd3bdba3 seems appropriate to me.
    
    Yes, I was keeping those URLs specifically to document intermediate
    certificate usage, but now that we have documentation of how to set up
    intermediates, we don't need it anymore.
    
    -- 
      Bruce Momjian  <bruce@momjian.us>        https://momjian.us
      EnterpriseDB                             https://enterprisedb.com
    
      The usefulness of a cup is in its emptiness, Bruce Lee
    
    
    
    
    
  26. Re: Stale external URL in doc?

    Kyotaro Horiguchi <horikyota.ntt@gmail.com> — 2020-07-22T02:37:07Z

    At Sat, 18 Jul 2020 22:48:47 +0900, Michael Paquier <michael@paquier.xyz> wrote in 
    > On Fri, Jul 17, 2020 at 02:03:18PM +0900, Michael Paquier wrote:
    > > It would be better to get all that fixed and backpatched. Is somebody
    > > already looking into that?
    > 
    > I have been through this set, and applied the changes as of 045d03f & 
    > friends.  There was an extra URL broken in 9.5 and 9.6 related to the
    > passphrase FAQ.
    
    Thanks!
    
    regards.
    
    -- 
    Kyotaro Horiguchi
    NTT Open Source Software Center