From: pf@pfortin.com
To: pgsql-general@lists.postgresql.org
Subject: Re: cache lookup failed for function 0
Date: Sat, 30 Sep 2023 14:32:55 -0400
Message-ID: <20230930143255.0d278307@pfortin.com> (raw)
In-Reply-To: <1561293.1696094414@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>
On Sat, 30 Sep 2023 13:20:14 -0400 Tom Lane wrote:
>pf@pfortin.com writes:
>> Python script and sample file attached...
>
>This runs fine for me, both in HEAD and 15.4.
>
>(Well, it fails at the last GRANT, seemingly because you wrote
>"{table}" not "{TABLE}". But the COPY goes through fine.)
Sorry, I ripped out some other test code which would have been
unnecessarily confusing; but couldn't check the remaining bits due to the
prior failure...
>Assuming that you verified that this specific test case fails
>for you, we're down to just a couple of theories:
>
>1. There's some relevant info you didn't supply yet (is it
>really a completely plain-vanilla installation? Maybe some
>odd choice of locale?)
As vanilla as it gets... Standard locale (C). The only odd thing that
happened: a system update the other day installed and started something
called tracker-miners which I was not happy with:
https://bugs.mageia.org/show_bug.cgi?id=32340
I was quite upset that the distro guys would install/run what they thought
could be a "cool" tool (as you'll see in the above link).
>2. There's something wrong with your Postgres installation.
Scary; but that's what I'm suspecting too now...
>It's hard to get much further than that with the info that
>we have.
Understood; I wasn't sure which rabbit hole to go down; but this is
starting to smell like a DB issue... I'll see about re-installing the
server and pray the DB is sane... If the above tracker-miners found my
postgres installation and added something to it; then I will be EXTREMELY
upset...
Thanks for confirming my simple SQL runs...
> regards, tom lane
Thanks Tom!
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: <20230930143255.0d278307@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>
* 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