Re: Remove useless int64 range checks on BIGINT sequence MINVALUE/MAXVALUE values

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Greg Nancarrow <gregn4422(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove useless int64 range checks on BIGINT sequence MINVALUE/MAXVALUE values
Date: 2021-07-04 08:53:06
Message-ID: CAApHDvo7jRz=Gzb27SF0+Neu5PSYErsmTPS2xZtbxHeu5hwa_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 3 Jul 2021 at 22:44, Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> I don't think this is a good change.

> I think we should leave it as is.

I'm inclined to agree.

When I mentioned adding a comment I'd not imagined it would be quite
so verbose. Plus, I struggle to imagine there's any compiler out there
that someone would use that wouldn't just remove the check anyway. I
had a quick click around on https://godbolt.org/z/PnKeq5bsT and didn't
manage to find any compilers that didn't remove the check.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2021-07-04 09:35:09 Re: rand48 replacement
Previous Message Dean Rasheed 2021-07-04 08:47:41 Re: rand48 replacement