Re: BUG #16939: Plural interval for negative singular

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, neverov(dot)max(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16939: Plural interval for negative singular
Date: 2021-04-26 16:45:34
Message-ID: 2266336.1619455534@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Sun, Apr 25, 2021 at 04:57:26AM -0700, Noah Misch wrote:
>> Let's not change from one popular spelling to another when doing so creates a
>> compatibility hazard. That is to say, I think PostgreSQL would be better with
>> this patch reverted.
>>
>> If we did want to standardize on singular for -1, EVALUATE_MESSAGE_PLURAL()
>> would be a key bit of code to change.

> Oh, good point. I think we should just pick one and be consistent --- I
> don't care which we choose.

I agree with Noah's opinion that we should stick to the historical
behavior in the interval I/O functions. There is not enough solidity
in the "this is grammatically wrong" argument to justify taking any
risk of application breakage, and it seems like there is some risk of
that there.

For the sorts of human-readable messages that EVALUATE_MESSAGE_PLURAL
tends to be used for, I don't think there's a reason to worry that
we might break applications if we change it. So I don't have a
strong opinion about what to do there. Still, by the same token
that the grammatical argument is weak, I lean towards not spending
effort on changing it.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2021-04-26 16:54:35 Re: BUG #16939: Plural interval for negative singular
Previous Message Bruce Momjian 2021-04-26 16:31:16 Re: BUG #16939: Plural interval for negative singular