Re: psql "\d" no longer working
| От | Adrian Klaver |
|---|---|
| Тема | Re: psql "\d" no longer working |
| Дата | |
| Msg-id | 1e4482c4-9c86-f36a-e29a-6a07d6bb2993@aklaver.com обсуждение исходный текст |
| Ответ на | Re: psql "\d" no longer working (Ron <ronljohnsonjr@gmail.com>) |
| Ответы |
Re: psql "\d" no longer working
|
| Список | pgsql-general |
On 2/12/23 08:49, Ron wrote: > On 2/12/23 03:02, Rob Sargent wrote: >> >> >> 2023-02-10 13:42:55.214 MST [524159] STATEMENT: SELECT >> c.relchecks, c.relkind, c.relhasindex, c.relhasrules, >> c.relhastriggers, c.relhasoids, '', c.reltablespace, CASE WHEN >> c.reloftype = 0 THEN '' ELSE >> c.reloftype::pg_catalog.regtype::pg_catalog.text END, c.relpersistence >> FROM pg_catalog.pg_class c >> LEFT JOIN pg_catalog.pg_class tc ON (c.reltoastrelid = >> tc.oid) >> WHERE c.oid = '219319'; >> 2023-02-10 13:43:01.143 MST [524159] ERROR: column c.relhasoids >> does not exist at character 80 >> >> but I don't see any other issue in the log file. >> >> I have yet to find another broken meta-command and no sql of mine has >> failed along similar lines as had "\d" >> >> Any pointers much appreciated. >> > > What is your search_path set to? I doubt that is the problem as the issue is the column in the table not finding the table. pg_class.relhasoids no longer exists 12+, so the post from Georg is probably pointing in the right direction. > > -- > Born in Arizona, moved to Babylonia. -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: