Hi
Thanks for all the help, and a couple of offlist suggestions.
We have fixed the problem by copying all of the data (160GB) to a
partitioned table, replacing the trigger with table column defaults for
timestamp and sequence values.
As a result, all is working ok.
Thank you, once again
Simon
Simon Windsor writes:
> Since then, large bulk inserts of configuration changes are failing with
> this Error, but adhoc and small changes are working ok.
Might it be that things work as long as the trigger is only tasked with
redirecting to the same child table (or limited set of child tables)
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 wee
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
Simon Windsor writes:
> I have just upgraded a Db from pg 10.5 to pg11.4 and almost immediately we
> are seeing errors like
> ERROR,XX000,"cache lookup failed for type 22079"
> When inserting into a a partitioned table. About 30% of inserts are
> reporting this error.
Hmm ... can you show the ful
