Re: Error XX000 After pg11 upgrade

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Error XX000 After pg11 upgrade
Date: 2019-08-16 00:11:21
Message-ID: 48a48d13-8f8e-19be-371f-ef129ff972dd@archidevsys.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 16/08/2019 04:35, Simon Windsor wrote:
> Hi
>
> The Full system used to in an Oracle DB and was ported to Postgres 9.5
> about 2+ years ago, and partitioned using inheritance tables.
>
> Since then pg_upgrade has been used to upgrade to pg10 (with apt
> upgrade to take to 10.5 occasionally).
>
> Last week, pg_upgrade was againn used to upgrade to pg11.4.
>
> Since then, large bulk inserts of configuration changes are failing
> with this Error, but adhoc and small changes are working ok.
>
> The actual error is reported by a Java process
>
> Caused by: org.postgresql.util.PSQLException: ERROR: cache lookup
> failed for type 22079
>   Where: SQL statement "insert into configObjectsFull_2019 values
> (new.*)"
> PL/pgSQL function configobjectsfull_insert_trigger() line 28 at SQL
> statement
>     at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2310)
>     at
>
> The DB Tableand Trigger are attached.
>
> As you can see, the id and timestamp are set on insert, and are used
> to determine the partition used.
>
> This issue started after the upgrade to pg11, pg10 and pg9 had no
> problems.
>
> Any ideas would be appreciated.

[...]

Probably will make no difference, but have you considered testing using
pg 11.5?  It would at least rule out a lot of Red Herrings!

Cheers,
Gavin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2019-08-16 00:28:06 Re: Error XX000 After pg11 upgrade
Previous Message Igor Neyman 2019-08-15 23:07:21 RE: Variable constants ?