pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pf@pfortin.com
Cc: pgsql-general@lists.postgresql.org
Subject: Re: cache lookup failed for function 0
Date: Sun, 01 Oct 2023 10:32:33 -0400
Message-ID: <1717206.1696170753@sss.pgh.pa.us> (raw)
In-Reply-To: <20231001015759.4a31b55a@pfortin.com>
References: <20230929163739.3bea46e5.pfortin@pfortin.com>
	<8fd58b4c-ef57-3218-b7e3-f087e15db784@aklaver.com>
	<20230930100132.44da3c45@pfortin.com>
	<f9aa81f1-1977-4e0f-b2f8-341b68e5c05a@aklaver.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>

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





view thread (16+ messages)

Message-ID: <1717206.1696170753@sss.pgh.pa.us>
Permalink:  ../1717206.1696170753@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1717206.1696170753@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pf@pfortin.com
  Subject: Re: cache lookup failed for function 0
  In-Reply-To: <1717206.1696170753@sss.pgh.pa.us>
  References: <20230929163739.3bea46e5.pfortin@pfortin.com> <8fd58b4c-ef57-3218-b7e3-f087e15db784@aklaver.com> <20230930100132.44da3c45@pfortin.com> <f9aa81f1-1977-4e0f-b2f8-341b68e5c05a@aklaver.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> <1717206.1696170753@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox