p...@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
Hi Adrian & Tom,
On Sat, 30 Sep 2023 15:57:32 -0700 Adrian Klaver wrote:
>On 9/30/23 14:54, p...@pfortin.com wrote:
>> On Sat, 30 Sep 2023 13:40:37 -0700 Adrian Klaver wrote:
>>
>>> On 9/30/23 11:32, p...@pfortin.com wrote:
>
>>
>> As I told Tom, the "test" DB has this issue; the
Adrian Klaver writes:
> On 9/30/23 14:54, p...@pfortin.com wrote:
>> 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.
> Still there was an issue with a database. Did you track down what
On 9/30/23 14:54, p...@pfortin.com wrote:
On Sat, 30 Sep 2023 13:40:37 -0700 Adrian Klaver wrote:
On 9/30/23 11:32, p...@pfortin.com wrote:
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.
On Sat, 30 Sep 2023 13:40:37 -0700 Adrian Klaver wrote:
>On 9/30/23 11:32, p...@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
On 9/30/23 11:32, p...@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:
On Sat, 30 Sep 2023 13:20:14 -0400 Tom Lane wrote:
>p...@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
p...@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.)
Assuming that you verified that this specific test case
On Sat, 30 Sep 2023 08:50:45 -0700 Adrian Klaver wrote:
>On 9/30/23 07:01, p...@pfortin.com wrote:
>> Hi Adrian,On Fri, 29 Sep 2023 14:27:48 -0700 Adrian Klaver wrote:
>>
>>> On 9/29/23 1:37 PM, p...@pfortin.com wrote:
Hi,
>
>>> I'm going to say it is the
>>>
>>> ( -- import only a
. 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 cau
On 9/30/23 07:01, p...@pfortin.com wrote:
Hi Adrian,On Fri, 29 Sep 2023 14:27:48 -0700 Adrian Klaver wrote:
On 9/29/23 1:37 PM, p...@pfortin.com wrote:
Hi,
I'm going to say it is the
( -- import only a subset of columns
I suspect the -- comment is the issue.
I wish it was that easy.
Ignore this message; I wondered where it went to -- Looks like I
accidentally hit Ctrl+Enter; just did that to another... SIGH...
On Sat, 30 Sep 2023 09:30:08 -0400 p...@pfortin.com wrote:
>On Fri, 29 Sep 2023 14:27:48 -0700 Adrian Klaver wrote:
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
w 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
tead. 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 somet
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&quo
16 matches
Mail list logo
