From: pf@pfortin.com
To: pgsql-general@lists.postgresql.org
Subject: Re: cache lookup failed for function 0
Date: Sat, 30 Sep 2023 12:33:06 -0400
Message-ID: <20230930123306.12d10df2@pfortin.com> (raw)
In-Reply-To: <1418544.1696026062@sss.pgh.pa.us>
References: <20230929163739.3bea46e5.pfortin@pfortin.com>
<1418544.1696026062@sss.pgh.pa.us>
On Fri, 29 Sep 2023 18:21:02 -0400 Tom Lane wrote:
>pf@pfortin.com writes:
>> As a test, rather than use INSERT, I recently wrote a python test script
>> to import some 8M & 33M record files with COPY instead. These worked with
>> last weekend's data dump. Next, I wanted to look into importing a subset
>> of columns using the below logic; but I'm getting "ERROR: cache lookup
>> failed for function 0". Re-running the same full imports that worked
>> Saturday, I now get the same error.
>
>> Could something in the DB cause this "function" error?
>
>"cache lookup failed" certainly smells like a server internal error,
>but we'd have heard about it if the trivial case you show could reach
>such a problem. I'm thinking there's things you haven't told us.
>What extensions do you have installed? Maybe an event trigger?
I have one production DB with fuzzystrmatch installed; but it's not in
any other DB. I'm trying to import into a test DB, and not yet at the
point of understanding or using triggers. This is a very simple setup,
other than the volume of data. The production DB has many tables, mostly
in the range of 8M-33M rows.
>Also, the reference to ENCODING 'ISO-8859-1' makes me wonder what
>encoding conversion is being performed.
The source files are mostly UTF-8; some files have the 1/2 (0xbd)
character in street addresses, hence the ISO...
> regards, tom lane
Thanks,
Pierre
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: pf@pfortin.com
Subject: Re: cache lookup failed for function 0
In-Reply-To: <20230930123306.12d10df2@pfortin.com>
References: <20230929163739.3bea46e5.pfortin@pfortin.com> <1418544.1696026062@sss.pgh.pa.us> <20230930123306.12d10df2@pfortin.com>
* 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