Re: bulk typos - Mailing list pgsql-hackers

From Tom Lane
Subject Re: bulk typos
Date
Msg-id 623992.1603660328@sss.pgh.pa.us
Whole thread Raw
In response to Re: bulk typos  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
Heikki Linnakangas <hlinnaka@iki.fi> writes:
> On 25/10/2020 21:48, Justin Pryzby wrote:
>> Heikki, do you remember what this means ?
>> +++ b/src/backend/catalog/storage.c
>> + * NOTE: the list is kept in TopMemoryContext to be sure it won't disappear
>> + * unbetimes.  It'd probably be OK to keep it in TopTransactionContext,
>> + * but I'm being paranoid.

> Heh, even though I was the last one to touch that line according to git
> blame, I just moved it from smgr.c. Looks like Tom wrote it in 2004. I
> guess it means "too early". That would make sense from the context.

Sorry about that, I was being a little whimsical I suppose.

Doing a bit of research, I see the OED defines "betimes" as

    [archaic] Before the usual or expected time; early.
    ‘next morning I was up betimes’

"unbetimes" doesn't seem to be a recognized word ... and now that I look
at this, if it did exist it would mean "too late" which is backwards.

I'd suggest "untimely" if you want to wax poetic, or "too soon" if
you prefer prose that plods.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Supporting = operator in gin/gist_trgm_ops
Next
From: Justin Pryzby
Date:
Subject: Re: [doc] remove reference to pg_dump pre-8.1 switch behaviour