| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Venkata B Nagothi <nag1010(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres upgrade 12 - issues with OIDs |
| Date: | 2021-05-16 12:57:32 |
| Message-ID: | CAApHDvogn441-RfRNOAwB8mPzgeWovR9gqgmBcmXq=EGhpwqkg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 16 May 2021 at 13:00, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Saturday, May 15, 2021, Venkata B Nagothi <nag1010(at)gmail(dot)com> wrote:
>> Below is the query generating the error :
>>
>> STATEMENT: SELECT c.relname AS table_name, c.relhaspkey AS has_primary_key FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n WHERE c.relkind = 'r' AND c.relnamespace = n.oid AND n.nspname = $1
>>
>> Any advice on how bad it is and how to get rid of it would be great.
>
>
> Figure out what is issuing the query and either fix it or upgrade to a version that has been fixed.
Just in addition to that, the relhaspkey column was removed in v11.
There's mention of this and a hint at what you might want to do to
work around the removal of the column in the release notes for that
version: https://www.postgresql.org/docs/release/11.0/
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Condor | 2021-05-16 17:54:20 | Re: Question about integer out of range in function |
| Previous Message | Julien Rouhaud | 2021-05-16 12:45:02 | Re: Empty tablespace directory after restore with psql -d dbname -f dump.sql |