> We removed the pg_attrdef.adsrc catalog column a couple versions back. > You're evidently using quite an old version of whichever client-side > library is issuing this command. You need to get a more up-to-date copy > that knows what to do instead.
Tom,
In what version was that removed? Now I have postgresql-12.7 installed and when I try to access the activitytypes table it still fails with the same error:
2021-06-07 10:36:38.304 PDT [29537] LOG: starting PostgreSQL 12.7 on x86_64-slackware-linux-gnu, compiled by gcc (GCC) 5.5.0, 64-bit 2021-06-07 10:36:38.304 PDT [29537] LOG: listening on IPv4 address "127.0.0.1", port 5432 2021-06-07 10:36:38.310 PDT [29537] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" 2021-06-07 10:36:38.322 PDT [29538] LOG: database system was shut down at 2021-06-07 10:36:17 PDT 2021-06-07 10:36:38.330 PDT [29537] LOG: database system is ready to accept connections 2021-06-07 14:19:45.491 PDT [31353] ERROR: column pg_attrdef.adsrc does not exist at character 128 2021-06-07 14:19:45.491 PDT [31353] STATEMENT: select pg_attribute.attname, pg_attribute.atttypid::int, pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod, pg_attrdef.adsrc from pg_class, pg_attribute left join pg_attrdef on (pg_attrdef.adrelid = pg_attribute.attrelid and pg_attrdef.adnum = pg_attribute.attnum) where pg_table_is_visible(pg_class.oid) and pg_class.relname = 'activitytypes' and pg_attribute.attnum > 0 and pg_attribute.attrelid = pg_class.oid and pg_attribute.attisdropped = false order by pg_attribute.attnum
If all you did was upgrade the server, and not the client that is issuing the query, then, yes, you will get the same error, since the server isn't the problem.
