Re: please define 'statement' in the glossary

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, "petermittere@gmail.com" <petermittere@gmail.com>, "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
Date: 2025-07-14T17:45:58Z
Lists: pgsql-docs
On Monday, July 14, 2025, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> "David G. Johnston" <david.g.johnston@gmail.com> writes:
> > If we accept that we use the words statement and command interchangeably
> > then the sole remaining use of command here sticks out because now we
> have
> > to explain why commands are different from statements.  I'd rather just
> > remove the parenthetical.  It's poorly clarifying a point that it seems
> you
> > don't want to clarify more fully here.
>
> [ shrug... ]  I'm inclined to go back to the "command message" wording
> then.  I don't find "client-issued statement" to be helpful at all;
> in particular, it's flat wrong for the multi-statement-query-message
> case, because surely all those statements are client-issued.  I'm okay
> with this text leaving out nitpicky details, but it should leave the
> reader with a mental model that more or less matches reality.
>

Then let’s use command message.  It basically the moral equivalent to my
(technically, query) parenthetical.

David J.

Commits

  1. Doc: clarify description of current-date/time functions.

  2. Some editorial work on the documentation of the current-date/time