Error opening a postgres 12 database (via postbird or something like) -> column "relhasoids" does not exist

Asked

Viewed 1,015 times

0

I went to create a new postgres bank via Docker using image: 'postgres:alpine' and with it he took the latest version (12.0). When opening the bank with Postbird (which has this bug) and trying to open a table, gave the message:

0.8.2 - column "relhasoids" does not exist

and wouldn’t let the table open.

  • 2

    Note that it is not a Postgresql bug, this field was removed from the pg_class table of the system catalog in version 12. The bug is in Postbird that did not make the necessary modification.

  • Exactly, I’ll fix it. One problem that I found strange is that the tables fields were not visible in another manager (Heidisql), and became visible after changing the postgres version

  • I was having the same problem, I downgraded the Postgres to version 11 on my Docker and solved.

  • 1

    The issue was closed because it is a bug in application (caused by lack of update), and not an author’s programming problem.

  • @Bacco this does not fit into a problem of "common tools among programmers"?

  • 2

    @Hugol.F. common tool among programmers if it were in relation to use under normal conditions. Note that even closed, the question will remain a reasonable time on the site, enough to be consulted in similar cases, but is a temporary solution. The main objective of the site is to be a repository of knowledge about programming, in the form of questions and answers that serve a wide audience. Support issues or occasional problems end up slipping away a bit from the goal, and note that in the case, it would be a matter of reading the documentation and seeing what has changed (maybe that’s why the negatives).

  • 1

    Note that anyone who understands differently can vote to reopen, and with a few votes the community itself can open the post without relying on moderator. Still, there is the site [meta], which has extensive discussions on the procedures of the site, and you can question the situation for the community to evaluate as a whole.

Show 2 more comments

2 answers

2

I had this same problem today after downloading the postgre image v12. The problem is not in the database but in the postbird version. In version 12 of the postgre there was a structure change in the bank’s system tables. To solve just download this version of postbird compiled on 14/10/2019 -> https://postbird.paxa.kuber.host/2019_10_14.06_42-master-7a9e949

I hope I’ve helped!

  • The version 0.8.4 (64 - 7d97963) already this set to suit the V12 of postgres.

1

While searching a little on the internet, I realized that version 12 had some modifications that caused this, such as the removal of this field ai of tables from the system (or something like).

Surround the image by modifying to image: 'postgres:11.5-alpine' and was.

That is, use the version 11.5 to solve the problem.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.