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 1nKHz1-0003d2-AV for pgsql-docs@arkaria.postgresql.org; Wed, 16 Feb 2022 10:56:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nKHz0-0008VP-4P for pgsql-docs@arkaria.postgresql.org; Wed, 16 Feb 2022 10:56:26 +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 ) id 1nKHyz-0008Uh-SI for pgsql-docs@lists.postgresql.org; Wed, 16 Feb 2022 10:56:25 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKHyv-0006VK-UR for pgsql-docs@lists.postgresql.org; Wed, 16 Feb 2022 10:56:25 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 419085C0120; Wed, 16 Feb 2022 05:56:20 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 16 Feb 2022 05:56:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=wTE0hGBtv5zrPwfKyc3Ap9jRGQxztDU9kQ/RG6Uckqo=; b=Gba6D6M+ HPEHPWuh0dUytkzo+7OarIm2wCOI/+ZxFg7rpMSDCC42rxmhG6L327Jrd8OxoWo5 13J5l5woR2cUMSE3eZnYVY+0GjRS1ksGhess6yMVryRX8SJkHqMVCcelBrHC9wqs 2/9DdADwqjjxU/aob+IlYvCbjmLRArT7lhAlVQHFGgGs7pa/9BYtztuZZ6/ZfaMg We6V8L4Hj5OOVBICoP4qZ2MrKCEztLU/642FZNv/Mq7UvKczl7cgO63MAUGBXNeq bAWrtgFVcyqhqQYyhqN9urX2RU5Va9EaAWYa4VPbRBQk6Qj1jag0IArsUpr0QDUJ samcuLo7K62U7A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrjeeigddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthejre dttdefjeenucfhrhhomheprfgvthgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdr vghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusgdrtghomheqnecuggftrfgrth htvghrnhepfeejgeehteeuhfevveduleeufedtjeetiefftedvudfhtdeifefgueettdev gefgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepph gvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 16 Feb 2022 05:56:18 -0500 (EST) Message-ID: <08bff51d-eb6b-381f-ca6b-08234828c754@enterprisedb.com> Date: Wed, 16 Feb 2022 11:56:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 Subject: Re: Does the POSITION() function takes into account the COLLATION... or not ?!? Content-Language: en-US To: pageorge@unice.fr, pgsql-docs@lists.postgresql.org References: <164494187300.23318.373331246819207718@wrigleys.postgresql.org> From: Peter Eisentraut In-Reply-To: <164494187300.23318.373331246819207718@wrigleys.postgresql.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 15.02.22 17:17, PG Doc comments form wrote: > Does the POSITION() function pretends taking into account the COLLATION ?? > or not ?? > > - If not, then why the hell is there this error message about > nondeterministic collations while the POSITION() doesn't care at all about > the COLLATION... > - If yes, then the first 6 lines of SQL above are returning the wrong > value... (are there any specific technical limitations here ?) I think you have that backwards. Your examples would only succeed if POSITION() supported nondeterministic collations, but it doesn't.