Re: February 9th, 2023 Release links to a missing page

From: Kirk Wolak <wolakk(at)gmail(dot)com>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: February 9th, 2023 Release links to a missing page
Date: 2023-02-19 20:55:59
Message-ID: CACLU5mR9L7BVUScYZnG9oQDB3Lx3eYvLKh2qRazAWGyuR1X-Kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Wed, Feb 15, 2023 at 2:05 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org>
wrote:

> On 2/15/23 1:59 PM, Kirk Wolak wrote:
> > It looks like a simple bad reference name:
> >
> > On this line:
> >
> > * Fix the |psql|
> > <https://www.postgresql.org/docs/current/app-psql.html> commands
> > |\sf| and |\ef| to handle SQL-language functions that have
> > SQL-standard function bodies
> > <https://www.postgresql.org/docs/currenet/sql-createprocedure.html> (i.e.
> |BEGIN ATOMIC|).
> ...
> The end of the URL is correct. The problem is "currenet" should be
> "current". I've made that correction. Thanks!
>
> > Side Note:
> > On such a posting is there no direct link to SUBMIT a correction (by
> > design?)
>
> The release announcements go through the news system, which does not
> have a feedback collection mechanism as anyone can post news. Emailing
> pgsql-docs, or even better pgsql-www, seems to be good enough for this
> case as we can quickly fix it, but I'm open to other suggestions.
>
> Thanks,
>
> Jonathan
>

Thank you. Good answer as well... I figured out to just send it here...

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Jonathan S. Katz 2023-02-19 21:55:39 Re: February 9th, 2023 Release links to a missing page
Previous Message PG Doc comments form 2023-02-19 03:10:43 Transaction wraparound and read committed isolation level