| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pf(at)pfortin(dot)com |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: cache lookup failed for function 0 |
| Date: | 2023-10-01 14:32:33 |
| Message-ID: | 1717206.1696170753@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
pf(at)pfortin(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ireneusz Pluta | 2023-10-01 17:04:42 | Re: Gradual migration from integer to bigint? |
| Previous Message | Phillip Diffley | 2023-10-01 13:35:31 | What changes to a table cannot be detected by a trigger? |