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

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove useless int64 range checks on BIGINT sequence MINVALUE/MAXVALUE values
Date: 2021-07-12 18:50:23
Message-ID: 647a268a-bd77-5e1c-eb4d-24b269921a8e@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12.07.21 10:44, David Rowley wrote:
> What I was trying to get to here was something that was more
> reasonable that might make sense to commit. I'm just not certain
> where Peter stands on this now that the latest patch is a net zero
> when it comes to adding lines. Peter?

Your version looks better to me than the original version, but I'm still
-0.05 on changing this at all.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-07-12 18:51:37 Re: Partition Check not updated when insert into a partition
Previous Message Tom Lane 2021-07-12 18:49:12 Re: "debug_invalidate_system_caches_always" is too long