Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sj08H-00CVix-Cc for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 17:37:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sj08D-00AIWa-Vy for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 17:37:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sj08C-00AIW3-I8 for pgsql-general@lists.postgresql.org; Tue, 27 Aug 2024 17:37:26 +0000 Received: from fout8-smtp.messagingengine.com ([103.168.172.151]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sj08A-001idK-5j for pgsql-general@lists.postgresql.org; Tue, 27 Aug 2024 17:37:23 +0000 Received: from phl-compute-05.internal (phl-compute-05.nyi.internal [10.202.2.45]) by mailfout.nyi.internal (Postfix) with ESMTP id 4A47F138FFA6; Tue, 27 Aug 2024 13:37:20 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-05.internal (MEProxy); Tue, 27 Aug 2024 13:37:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1724780240; x=1724866640; bh=OsCfoELP8DKQdRNaQ0pmGGqC6iIE5EQ635FEFL3UB6Y=; b= yumgzsEbXQlj//nQaCPJB0iRKisnR9Kj9cHurSW2U7Tw9PgoJ8jIJZZau63s1uUM zWBwL75QqG/C1pNdK+MnMVEP5eS1OHcePOibYW6hAVRR71ZrZ1AeSeyxCeSVMaUU j4jir8vKMrmyiIdpRrptny1OSS8wjOqXBshotjHEflli1xAoUde9uX6gXSFNgiBB 1yUURAG6UTwHFAMoAPsWm4DxqLOlgARDzwA0XdLMX7kLA3m+xifmcDnl5JTOhM/h ElyLAbUwrlYft1i3bJ8st3PMcXhby/k+96WHRCcEVKDH4svQAgVSZwsT15sNSRk/ sWGPPDPMCwYWLXF0rcHwjw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1724780240; x= 1724866640; bh=OsCfoELP8DKQdRNaQ0pmGGqC6iIE5EQ635FEFL3UB6Y=; b=s hzkISSa2I2sl8UMZEB66BBgABMc+jyNOJCBGAWqnyCtuJe988EmBmHdfCZHciywG 3oc7Ks9w7B7uT9Gv2IM8/r2PzRcGp/s9abBjswC10ZgFWfAHXAqkMl8RTRaONppi +TP8RtcIEIBAYEE5X7x+kNXMqP1ThUq3ltXzrFgLk1Ols6Xoi+OBCJ9BDoTdscIY tIxy+KeQnwgGamBlZtGOxEAM4m4Mho+gXE3ZjJjhqPM01GotQmiRqC0q70iJtZ2y vDgvCT8gfuQmcxx2FcEhhpSygxC9h0QXho7qsON5up+tcU+V0xuHqPhLarntypt/ 5JkQnSQuAcDSiu/+vf8Ig== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudeftddguddugecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepkfffgg gfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgv rhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrg htthgvrhhnpeffleegieefgfevudehtdfhkeeutdffjeevgeffgeejvedthefgudeiteef heejheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtthho pedvpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehpohhsthhgrhgvshhqlhesth hhvghfrhgvvggtrghtrdhorhhgpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgrlhes lhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 27 Aug 2024 13:37:19 -0400 (EDT) Message-ID: <572cc9d2-a981-4f0e-802a-69515dac1722@aklaver.com> Date: Tue, 27 Aug 2024 10:37:17 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Strange behaviors with ranges To: Jean-Christophe Boggio , pgsql-general@lists.postgresql.org References: <77691006-45f1-4ef9-bc1b-2eecd44f7d0d@thefreecat.org> Content-Language: en-US From: Adrian Klaver In-Reply-To: <77691006-45f1-4ef9-bc1b-2eecd44f7d0d@thefreecat.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/27/24 10:29 AM, Jean-Christophe Boggio wrote: > Hello, > > I have 2 very confusing behaviors when using ranges. > > It all started with this query: > >     WITH rangespaliers AS ( >         SELECT numrange( qtep1+1   , qtep2,  '[]') AS rangep FROM > paliers JOIN tmp_limitcontrats USING(idcontrat) > --        SELECT numrange( qtep1+1   , qtep2,  '[]') AS rangep FROM > paliers WHERE idcontrat=1003 >     ) >     ,rangespaliers2 AS ( >         select * >         FROM rangespaliers >         WHERE rangep <> NUMRANGE(NULL, NULL) -- ERROR IS HERE >     ) >     select * from rangespaliers2; > > When I run this query, I get the error "Range lower bound must be less > than or equal to range upper bound". > > (a) If I comment out the line marked "ERROR IS HERE", I don't have an > error (but I'm missing the filter of course). > > (b) Also, if I uncomment line 3 and comment out line 2, I get the > correct behavior. Very strange thing is that tmp_limitcontrats has only > one row which contains "idcontrat=1003". What does: SELECT numrange( qtep1+1 , qtep2, '[]') AS rangep FROM paliers WHERE idcontrat=1003 return? > > This fails on PG 16.4 and 15.7 > > Thanks a lot for your enlightenment. > -- Adrian Klaver adrian.klaver@aklaver.com