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 1qmxVr-009Zfa-Am for pgsql-general@arkaria.postgresql.org; Sun, 01 Oct 2023 14:33:39 +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 1qmxVp-00Cwd0-6e for pgsql-general@arkaria.postgresql.org; Sun, 01 Oct 2023 14:33:37 +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 1qmxVo-00Cwbc-Qh for pgsql-general@lists.postgresql.org; Sun, 01 Oct 2023 14:33:36 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qmxVm-007cWs-8i for pgsql-general@lists.postgresql.org; Sun, 01 Oct 2023 14:33:35 +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 391EWXIi1717207; Sun, 1 Oct 2023 10:32:33 -0400 From: Tom Lane To: pf@pfortin.com cc: pgsql-general@lists.postgresql.org Subject: Re: cache lookup failed for function 0 In-reply-to: <20231001015759.4a31b55a@pfortin.com> References: <20230929163739.3bea46e5.pfortin@pfortin.com> <8fd58b4c-ef57-3218-b7e3-f087e15db784@aklaver.com> <20230930100132.44da3c45@pfortin.com> <20230930123527.4efb81e4@pfortin.com> <1561293.1696094414@sss.pgh.pa.us> <20230930143255.0d278307@pfortin.com> <1aa75625-219e-45f1-bcfc-d2c9ee118cb6@aklaver.com> <20230930175414.7cf0dc2f@pfortin.com> <4455c6d7-29d5-4776-8153-8db67c05645a@aklaver.com> <20231001015759.4a31b55a@pfortin.com> Comments: In-reply-to pf@pfortin.com message dated "Sun, 01 Oct 2023 01:57:59 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1717205.1696170753.1@sss.pgh.pa.us> Date: Sun, 01 Oct 2023 10:32:33 -0400 Message-ID: <1717206.1696170753@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk pf@pfortin.com writes: > I see the string "SET client_encoding = 'WIN1252';" in the dump -- some > files come from a remote colleague; but this has never been an issue > before... Hah! If I create the test database with encoding WIN1252 then your test fails as described. It *should* be complaining that it doesn't know how to convert from ISO-8859-1 to WIN1252, but BeginCopyFrom is neglecting to check for failure of FindDefaultConversionProc. Will fix that, thanks for the report. In the meantime, if use of WIN1252 was intentional then you'll need to find another way to transcode the data that was in that encoding. Probably, running your database in UTF8 is the best choice -- we can convert most anything to that. regards, tom lane