pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
February 9th, 2023 Release links to a missing page
6+ messages / 2 participants
[nested] [flat]

* February 9th, 2023 Release links to a missing page
@ 2023-02-15 18:59  Kirk Wolak <wolakk@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Kirk Wolak @ 2023-02-15 18:59 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org

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 link for function bodies is called: "sql-create*procedure*.html"
and I believe it should be "sql-create*function*.html"

Side Note:
On such a posting is there no direct link to SUBMIT a correction (by
design?)

Thanks,

Kirk Out!

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: February 9th, 2023 Release links to a missing page
@ 2023-02-15 19:05  Jonathan S. Katz <jkatz@postgresql.org>
  parent: Kirk Wolak <wolakk@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Jonathan S. Katz @ 2023-02-15 19:05 UTC (permalink / raw)
  To: Kirk Wolak <wolakk@gmail.com>; pgsql-docs@lists.postgresql.org

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 link for function bodies is called: "sql-create*procedure*.html"
> and I believe it should be "sql-create*function*.html"

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


Attachments:

  [application/pgp-signature] OpenPGP_signature (839B, ../../93aa43ab-986d-8e98-0b59-473fdb470743@postgresql.org/2-OpenPGP_signature)
  download

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: February 9th, 2023 Release links to a missing page
@ 2023-02-19 20:55  Kirk Wolak <wolakk@gmail.com>
  parent: Jonathan S. Katz <jkatz@postgresql.org>
  0 siblings, 1 reply; 6+ messages in thread

From: Kirk Wolak @ 2023-02-19 20:55 UTC (permalink / raw)
  To: Jonathan S. Katz <jkatz@postgresql.org>; +Cc: pgsql-docs@lists.postgresql.org

On Wed, Feb 15, 2023 at 2:05 PM Jonathan S. Katz <jkatz@postgresql.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...

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: February 9th, 2023 Release links to a missing page
@ 2023-02-19 21:55  Jonathan S. Katz <jkatz@postgresql.org>
  parent: Kirk Wolak <wolakk@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Jonathan S. Katz @ 2023-02-19 21:55 UTC (permalink / raw)
  To: Kirk Wolak <wolakk@gmail.com>; +Cc: pgsql-docs@lists.postgresql.org

On 2/19/23 3:55 PM, Kirk Wolak wrote:
> On Wed, Feb 15, 2023 at 2:05 PM Jonathan S. Katz <jkatz@postgresql.org 
> <mailto:jkatz@postgresql.org>> wrote:
> 
>     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.
> 
> Thank you.  Good answer as well...   I figured out to just send it here...

Well, that gives me an idea. In the release announcement, we could put a 
line that says "You can send any corrections or suggestions to the 
public pgsql-www@lists.postgresql.org mailing list" or something like 
that. That way, it would remove the guessing on what to do.

Jonathan


Attachments:

  [application/pgp-signature] OpenPGP_signature (839B, ../../f1498d1d-ddd8-0c83-fee6-122875b1dad4@postgresql.org/2-OpenPGP_signature)
  download

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: February 9th, 2023 Release links to a missing page
@ 2023-02-21 01:57  Kirk Wolak <wolakk@gmail.com>
  parent: Jonathan S. Katz <jkatz@postgresql.org>
  0 siblings, 1 reply; 6+ messages in thread

From: Kirk Wolak @ 2023-02-21 01:57 UTC (permalink / raw)
  To: Jonathan S. Katz <jkatz@postgresql.org>; +Cc: pgsql-docs@lists.postgresql.org

On Sun, Feb 19, 2023 at 4:55 PM Jonathan S. Katz <jkatz@postgresql.org>
wrote:

> On 2/19/23 3:55 PM, Kirk Wolak wrote:
> > On Wed, Feb 15, 2023 at 2:05 PM Jonathan S. Katz <jkatz@postgresql.org
> > <mailto:jkatz@postgresql.org>> wrote:
> >
> >     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.
> >
> > Thank you.  Good answer as well...   I figured out to just send it
> here...
>
> Well, that gives me an idea. In the release announcement, we could put a
> line that says "You can send any corrections or suggestions to the
> public pgsql-www@lists.postgresql.org mailing list" or something like
> that. That way, it would remove the guessing on what to do.
>
> Jonathan
>
Perfect...  I love this community!

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: February 9th, 2023 Release links to a missing page
@ 2023-02-21 14:50  Jonathan S. Katz <jkatz@postgresql.org>
  parent: Kirk Wolak <wolakk@gmail.com>
  0 siblings, 0 replies; 6+ messages in thread

From: Jonathan S. Katz @ 2023-02-21 14:50 UTC (permalink / raw)
  To: Kirk Wolak <wolakk@gmail.com>; +Cc: pgsql-docs@lists.postgresql.org

On 2/20/23 8:57 PM, Kirk Wolak wrote:
> On Sun, Feb 19, 2023 at 4:55 PM Jonathan S. Katz <jkatz@postgresql.org 

>     Well, that gives me an idea. In the release announcement, we could
>     put a
>     line that says "You can send any corrections or suggestions to the
>     public pgsql-www@lists.postgresql.org
>     <mailto:pgsql-www@lists.postgresql.org> mailing list" or something like
>     that. That way, it would remove the guessing on what to do.
> 
> Perfect...  I love this community!

Thanks. As I'd probably forget before the next update announcement, I 
sketched out the draft of it to ensure it included a line[1] around how 
to report corrections/suggestions.

Thanks again!

Jonathan

[1] 
https://git.postgresql.org/gitweb/?p=press.git;a=commitdiff;h=c5d98a4a9caece103205d1a213b11fa96086bd...


Attachments:

  [application/pgp-signature] OpenPGP_signature (839B, ../../8b27c72e-e3cd-972d-0cfb-7aae8c359b8e@postgresql.org/2-OpenPGP_signature)
  download

^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2023-02-21 14:50 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-02-15 18:59 February 9th, 2023 Release links to a missing page Kirk Wolak <wolakk@gmail.com>
2023-02-15 19:05 ` Jonathan S. Katz <jkatz@postgresql.org>
2023-02-19 20:55   ` Kirk Wolak <wolakk@gmail.com>
2023-02-19 21:55     ` Jonathan S. Katz <jkatz@postgresql.org>
2023-02-21 01:57       ` Kirk Wolak <wolakk@gmail.com>
2023-02-21 14:50         ` Jonathan S. Katz <jkatz@postgresql.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox