From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: David Harper <adh@sanger.ac.uk>, pgsql-docs@lists.postgresql.org
Subject: Re: Ambiguous language in Table 8.13. Special Date/Time Inputs [EXT]
In-reply-to: <20190709154825.egarmx2s5jyvft4e@momjian.us>
References: <156258047907.1181.11324468080514061996@wrigleys.postgresql.org>
 <20190709033234.ytbltfn25h5wvdbd@momjian.us>
 <8B4735A4-7B46-406A-B4F1-CBFA47D5E1BC@sanger.ac.uk>
 <20190709154825.egarmx2s5jyvft4e@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Tue, 09 Jul 2019 11:48:25 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25366.1562687915.1@sss.pgh.pa.us>
Date: Tue, 09 Jul 2019 11:58:35 -0400
Message-ID: <25367.1562687915@sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> Yes, I see what you mean now.  How is this patch, which uses "zero
> hour"?

Ugh.  Are we writing spy novels now?

I actually agree with your opinion that "midnight" is fine.
That text has been that way for over fifteen years[1], and
nobody's complained before that it was ambiguous.

But, if we're going to change it, let's just s/midnight/00:00:00/
and be done.  Making up fancy terminology doesn't improve matters.

			regards, tom lane

[1] git blame dates the text to commit 1b342df00 of 2002-11-11, and
apparently it was not new then, but I'm too lazy to dig further.