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 1stTMc-00Geyk-JC for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Sep 2024 14:51:35 +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 1stTMb-009ibk-M5 for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Sep 2024 14:51:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1stTMb-009ibb-DU for pgsql-bugs@lists.postgresql.org; Wed, 25 Sep 2024 14:51:33 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1stTMX-0012KP-Fp for pgsql-bugs@lists.postgresql.org; Wed, 25 Sep 2024 14:51:32 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 48PEpOKU3647706; Wed, 25 Sep 2024 10:51:24 -0400 From: Tom Lane To: "David G. Johnston" cc: "zengman@halodbtech.com" , "pgsql-bugs@lists.postgresql.org" Subject: =?UTF-8?Q?Re:_BUG_#18632:_Whether_you_need_to_consider_modifying_?= =?UTF-8?Q?the_array's_handling_of_delimiters=EF=BC=9F?= In-reply-to: References: <18632-15cedd7d4154ea2a@postgresql.org> Comments: In-reply-to "David G. Johnston" message dated "Wed, 25 Sep 2024 05:33:15 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3647704.1727275884.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 25 Sep 2024 10:51:24 -0400 Message-ID: <3647705.1727275884@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Wednesday, September 25, 2024, PG Bug reporting form < > noreply@postgresql.org> wrote: >> So should we consider modifying "array_in" to enhance the handling of >> separators to be more consistent with people's expectations? > A design being inflexible or not meeting people’s expectations is not a > bug. The system is behaving as documented. And we are not going to be > redefining how valid code is parsed here. Yeah, I seriously doubt that we could change array_in's behavior for single quotes (to wit, that they are not special in any way) without breaking existing applications. regards, tom lane