Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jM5vT-0003DM-F2 for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Apr 2020 08:19:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jM5vS-0000Ka-Cf for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Apr 2020 08:19:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <9erthalion6@gmail.com>) id 1jM5vS-0000KS-4W for pgsql-bugs@lists.postgresql.org; Wed, 08 Apr 2020 08:19:10 +0000 Received: from mail-wm1-x331.google.com ([2a00:1450:4864:20::331]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <9erthalion6@gmail.com>) id 1jM5vQ-0006sT-35 for pgsql-bugs@lists.postgresql.org; Wed, 08 Apr 2020 08:19:09 +0000 Received: by mail-wm1-x331.google.com with SMTP id y24so372674wma.4 for ; Wed, 08 Apr 2020 01:19:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=KNJRxC0ruOaiFvic+UtKa0P0LRlNa56wvSoSO29ojeU=; b=IskMq/oiFeb7l4om64M8qT6UlaZmnI1RpaLOgyUWZr/Hi5hkJKfSdRLn7OfdAmglOL 4LWLUA/Hyerw9T3IBiBLZp6TYHolQySh9ManuwRu3PoJOFCzCf4Dt2JmH2DybEd349i2 JFKy33gC3Y87VGX/gnUWtwXCz63d8sTmTPtlGHAtRXl+TMJ3AdiPnhFzjYT5Bf/eqMkz dWVQkCXacQrn5wR4/6vTaK9FrVB0BwQmzw8DKU2DxXcTxqxUJv3F9TaXyqMwMldGkR7O LilFzq/Lzd0fkaYJTosElpPNI45or7ndVfXKRDpKHW1f3jqSZiSonSVVzCgTb0m2xHni RfVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=KNJRxC0ruOaiFvic+UtKa0P0LRlNa56wvSoSO29ojeU=; b=Wz1nzmrHXLGyypwCGgmmiH2Sib9G8J4NdPV4zZm9wp3YGK0oX+7LcmjG7SJdPPlzkV 570acdDMWNk/QNXszKiq27RuW8IeCtjW88U4IwIN+4/U2xkaPFXpwjDo6rQeqKg59Vpv /xi7gdGYyCRwuxh04nKshxOCnUDxrzKR/62Ear2ltCne/qHLFEdoJo2RzSqRnqJSTDHf Kb06JFZubgSJ+vA+HW2Gkd67FbQByexKVqQrtzQxJU55kHETBVAjNMznWdcgZmrQ4pTk vyuxywU2o/YJOzrSLMxQ9+FZFkTW/NU9nwPOKa0y7KqZci0ZOBjkxNvSh1bM7xzIhfvZ N3jg== X-Gm-Message-State: AGi0PuYxGTLEDOqYVHZ3Mb0cO1i9QeAVv1ElVLrFBuv8bXBrTmUzB7UQ Ep2EmC+kd/T5OnIZkE3H+gI= X-Google-Smtp-Source: APiQypKltLc9XxHF3f2L/H3VtUtuB8m2ttbVU4KG53CQ5GSaPwenZh/BwZSezmrGi67eER3fbda2OQ== X-Received: by 2002:a1c:6885:: with SMTP id d127mr3430683wmc.33.1586333945351; Wed, 08 Apr 2020 01:19:05 -0700 (PDT) Received: from localhost (dslb-094-222-004-201.094.222.pools.vodafone-ip.de. [94.222.4.201]) by smtp.gmail.com with ESMTPSA id j6sm35603215wrb.4.2020.04.08.01.19.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Apr 2020 01:19:04 -0700 (PDT) Date: Wed, 8 Apr 2020 10:20:32 +0200 From: Dmitry Dolgov <9erthalion6@gmail.com> To: Michael Paquier Cc: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation Message-ID: <20200408082032.rbangeo24hhhaita@localhost> References: <16325-809194cf742313ab@postgresql.org> <20200328125303.4me6vetvzgebobw5@localhost> <20200401070842.GD142683@paquier.xyz> <20200401120117.qkmjxi3xrumbnd3s@localhost> <20200402020150.GA2803@paquier.xyz> <20200403152910.rsdc2yg7bisqaltb@localhost> <20200407074944.GA6655@paquier.xyz> <20200408060639.GG1606@paquier.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200408060639.GG1606@paquier.xyz> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On Wed, Apr 08, 2020 at 03:06:39PM +0900, Michael Paquier wrote: > > I was considering this stuff again, and I got cold feet regarding the > fact that we may be able to hit the case of a collation not set if the > type is collatable depending on how the restrictions now in place for > partition bound expressions get lifted in the future, so I have > committed what you sent as v1, after changing the first error message > to use "partition bound expression" and after adding a comment on top > of the new checks. Thanks!