42703 org postgresql util psqlexception error column t relhasoids does not exist

NaoNao

1,2832 gold badges6 silver badges8 bronze badges

I am able to reproduce your error if I am using Postgres v.12 and an older client (v.11 or earlier):

[root@def /]# psql -h 172.17.0.3
psql (11.5, server 12.0)
WARNING: psql major version 11, server major version 12.
         Some psql features might not work.
Type "help" for help.

postgres=# create table mytable (id int, name text);
CREATE TABLE
postgres=# table mytable;
 id | name 
----+------
(0 rows)

postgres=# d mytable;
ERROR:  column c.relhasoids does not exist
LINE 1: ...riggers, c.relrowsecurity, c.relforcerowsecurity, c.relhasoi...
                                                             ^
postgres=# 

This is because in v. 12, table OIDs are no longer treated as special columns, and hence the relhasoids column is no longer necessary. Please make sure you’re using a v. 12 psql binary so you don’t encounter this error.

You may not necessarily be using psql, so the more general answer here is to make sure you’re using a compatible client.

answered Oct 19, 2019 at 7:19

For anyone running Postgres as a Docker container:

Instead of running psql from the host, run it from inside the container e.g.

docker exec -it postgres_container_name psql your_connection_string

The Postgres image always ships with the corresponding—and thus always updated—version of psql so you don’t have to worry about having the correct version installed on the host machine.

answered Nov 7, 2019 at 11:52

If you’re using DataGrip, there’s an easy fix:

Try using «Introspect using JDBC metadata». This fixed it for me when (I think) I had a version mismatch between postgresql server and DataGrip client.

Under your connection settings -> Options tab -> check Introspect using JDBC metadata

According to https://www.jetbrains.com/help/datagrip/data-sources-and-drivers-dialog.html#optionsTab :

Switch to the JDBC-based introspector.

To retrieve information about database objects (DB metadata), DataGrip
uses the following introspectors:

1. A native introspector (might be unavailable for certain DBMS). The
   native introspector uses DBMS-specific tables and views as a source of
   metadata. It can retrieve DBMS-specific details and produce a more
   precise picture of database objects.

2. A JDBC-based introspector (available for all the DBMS). The JDBC-based
   introspector uses the metadata provided by the JDBC driver. It can
   retrieve only standard information about database objects and their
   properties.

Consider using the JDBC-based intorspector when the native
introspector fails or is not available.

The native introspector can fail, when your database server version is
older than the minimum version supported by DataGrip.

You can try to switch to the JDBC-based introspector to fix problems
with retrieving the database structure information from your database.
For example, when the schemas that exist in your database or database
objects below the schema level are not shown in the Database tool
window.

answered Nov 20, 2020 at 16:25

EutychusEutychus

3938 silver badges10 bronze badges

JL_SOJL_SO

1,6321 gold badge23 silver badges34 bronze badges

JocelynJocelyn

1,31211 silver badges20 bronze badges

I had this issue today, was unable to continue work due to this, strangely the application code is working fine.

Later, found this issue is only occurring if I use OmniDb client I use to connect to DB.

I have switched client to default pgAdmin 4 that comes with postgres installation & issue is not occurring anymore pgAdmin 4. Link: https://www.pgadmin.org/download/pgadmin-4-windows/

Its possible that OmniDb client might be older, but no time to troubleshoot it, using pgAdmin 4 for now.

Hope that helps.

answered Oct 19, 2019 at 9:32

Just update DataGrip solved this issue, Datagrip updated to version DataGrip 2019.3.3, Build #DB-193.6494.42, built on February 12, 2020, Now working

Just for DataGrip users!

answered Oct 2, 2020 at 17:10

answered Oct 20, 2019 at 0:23

Pankaj ShindePankaj Shinde

3,1932 gold badges35 silver badges43 bronze badges

answered Nov 25, 2020 at 7:20

Laurenz Albe

38.8k4 gold badges34 silver badges58 bronze badges

Laurenz AlbeLaurenz Albe

38.8k4 gold badges34 silver badges58 bronze badges

When used with quotes, Postgresql is case sensitive regarding identifier names like table names and columns names.
In your case, your column name may have been created with double quotes using a different case of price. Maybe it was created as "Price"? If so, just recreate it without quotes, or using the same case sensitivity of your queries.

I need to check it, but I think those quotes are added by EF when generating the queries.

I hope it helps.

Thanks Francisco, you are right, this issue is caused by case mismatch.
Is there way to switch Npgsql to case-insensitive mode apart from applying data annotations to the model columns ?

Hi, @fatim !
I’m glad you got it working.

Is there way to switch Npgsql to case-insensitive mode apart from applying data annotations to the model columns ?

I don’t know it yet. I need to check if we can make something about those quotes.
@Emill , do you have any idea if it is possible to remove those quotes from EF queries?
Thanks in advance.

Postgresql’s names are case-sensitive but for some strange reason the identifiers put in an sql query are automatically converted to lower case by the lexer unless they are surrounded by quotes.

If the properties of the models don’t match the column names, it is possible by using attributes to use other column names.

If requested, we could have some option to automatically convert CamelCase identifiers to lower_case_with_underlines to better fit the naming conventions used by .net and Postgresql.

You can use EF6’s own API to specify the database names on all classes and properties (some Linq on the model + EF6’s fluent API should do the trick).