pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: pf@pfortin.com
To: pgsql-general@lists.postgresql.org
Subject: Re: cache lookup failed for function 0
Date: Sat, 30 Sep 2023 17:54:14 -0400
Message-ID: <20230930175414.7cf0dc2f@pfortin.com> (raw)
In-Reply-To: <1aa75625-219e-45f1-bcfc-d2c9ee118cb6@aklaver.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>

On Sat, 30 Sep 2023 13:40:37 -0700 Adrian Klaver wrote:

>On 9/30/23 11:32, pf@pfortin.com wrote:
>> On Sat, 30 Sep 2023 13:20:14 -0400 Tom Lane wrote:
>>   
>
>> 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...  
>
>The script ran on my installation also. It would seem it is something on 
>your end. Has there been any issues with your machine and/or database 
>e.g. crashes or other odd behavior(not counting the tracker-miners update)?

As I told Tom, the "test" DB has this issue; the production and test1 DBs
are fine; I should have thought to check those first... Sorry for the
noise.

>FYI, since you are using psycopg2 you might want to use the built in 
>tools for:
>
>    a) Dynamic SQL
>	https://www.psycopg.org/docs/sql.html
>
>    b) COPY
>  	https://www.psycopg.org/docs/usage.html#using-copy-to-and-copy-from

Thanks for these links... They look very interesting.  Someone on this
list suggested Practical SQL by Anthony DeBarros which we're working
through...  He should see sales from all over the US now....  :)

We were working with a python script (using INSERT) someone wrote a couple
years ago; with my version using COPY[1], imports have gone from 2+ hours
to under a minute each for 8M and 33M row files.  If the above links help
even more that will be amazing!!  THANK YOU!!

[1] the script I sent is just a test script I threw together to check out
COPY features -- only started; but well impressed.


>> 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...  
>
> From here:
>
>https://github.com/GNOME/tracker-miners
>
>it looks like the software use SQLite for data storage.
>
>> 
>> Thanks for confirming my simple SQL runs...
>>   
>>> 			regards, tom lane  
>> 
>> Thanks Tom!
>> 
>>   
>





view thread (16+ messages)  latest in thread

Message-ID: <20230930175414.7cf0dc2f@pfortin.com>
Permalink:  ../20230930175414.7cf0dc2f@pfortin.com/
Also on:    postgresql.org/message-id/20230930175414.7cf0dc2f@pfortin.com

 · 

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: pf@pfortin.com
  Subject: Re: cache lookup failed for function 0
  In-Reply-To: <20230930175414.7cf0dc2f@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>

* 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