Rich Shepard <rshepard@xxxxxxxxxxxxxxx> writes: > 2021-06-07 08:47:21.108 PDT [6734] ERROR: column pg_attrdef.adsrc does not exist at character 128 > 2021-06-07 08:47:21.108 PDT [6734] 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 = 'industrytypes' and > pg_attribute.attnum > 0 and pg_attribute.attrelid = pg_class.oid and > pg_attribute.attisdropped = false order by pg_attribute.attnum Ah-hah, now we are getting somewhere. Yes, this seems much more consistent with your original symptoms, ie app connects but fails to see any tables. (Its error reporting is still poor, though.) > Fixing this error might well fix the issues I'm experiencing; I don't know > where to start. 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. regards, tom lane
