Re: please define 'statement' in the glossary

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> I dislike the word message.

> It would be nice if we could say/document: Command means top-level SQL;
> Statement references a sub-component of a command.

I think there are enough places where we use those words
interchangeably that it would be very difficult to get to a point of
consistently making the distinction.  Moreover, the distinction isn't
important for most purposes.  So I think the right route is to make
this para provide a self-contained description of what it's talking
about, rather than to reference a glossary entry that would likely
be misleading for many many other usages.

Perhaps the phrase "top-level statement" could be used, but I'd still
rather provide a parenthetical specification of what we mean by that.

I agree with Laurenz that we don't have to get into details as fine as
what happens with a multi-statement command message.  As long as we
can tie statement_timestamp() to the notion of receiving something
from the client, I think that's enough detail for here.  Somebody
who wants to probe the edges of that can read the code or experiment,
and the docs will have given them the right mind-set about what is
important.

			regards, tom lane