Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Heidi 10.2.0 does not process postgresql-10-postgis-2.4 properly

charmquark's profile image charmquark posted 4 weeks ago in General Permalink

I have the updated to latest version of Heidi, and I installed GIS (postgresql-10-postgis-2.4 )

The log of the heidiSQL shows below.

SET search_path TO 'public', '$user';
SELECT *, pg_table_size(QUOTE_IDENT(t.TABLE_SCHEMA) || '.' || QUOTE_IDENT(t.TABLE_NAME))::bigint AS data_length, pg_relation_size(QUOTE_IDENT(t.TABLE_SCHEMA) || '.' || QUOTE_IDENT(t.TABLE_NAME))::bigint AS index_length, c.reltuples, obj_description(c.oid) AS comment FROM "information_schema"."tables" AS t LEFT JOIN "pg_namespace" n ON t.table_schema = n.nspname LEFT JOIN "pg_class" c ON n.oid = c.relnamespace AND c.relname=t.table_name WHERE t."table_schema"='public';
/* Unknown datatype oid #1034 for "nspacl". Fall back to UNKNOWN. */
/* Unknown datatype oid #1034 for "relacl". Fall back to UNKNOWN. */
/* Unknown datatype oid #1009 for "reloptions". Fall back to UNKNOWN. */
/* Unknown datatype oid #194 for "relpartbound". Fall back to UNKNOWN. */
SELECT "p"."proname", "p"."proargtypes" FROM "pg_catalog"."pg_namespace" AS "n" JOIN "pg_catalog"."pg_proc" AS "p" ON "p"."pronamespace" = "n"."oid" WHERE "n"."nspname"='public';

PS: pgAdmin 4 displays properly

ansgar's profile image ansgar posted 4 weeks ago Permalink

What do you mean with "does not process"? Is there some error?

These "Unknown datatypes" are quite common in HeidiSQL on PostgreSQL - the data types are quite dynamically.

charmquark's profile image charmquark posted 4 weeks ago Permalink

Please find attached the screenshot of "Heidi Screenshot.png" , while in comparison PG admin shows differently

There is no error (that i can see )

2 attachment(s):
  • PGadmin
  • Heidi-Screenshot
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
ansgar's profile image ansgar posted 4 weeks ago Permalink

You're comparing HeidiSQL's "database" tab with the "extensions" area in PG admin? I don't get your point here.

charmquark's profile image charmquark posted 3 weeks ago Permalink

Hi, sorry for late reply. Im trying to demonstrate that it does not load/ show tables as pgpadmin eg schema's

ansgar's profile image ansgar posted 3 weeks ago Permalink

So HeidiSQL does not show some/all tables in your schema?

Your tables are not in the result of such a query?

SELECT *, pg_table_size(QUOTE_IDENT(t.TABLE_SCHEMA) || '.' || QUOTE_IDENT(t.TABLE_NAME))::bigint AS data_length, pg_relation_size(QUOTE_IDENT(t.TABLE_SCHEMA) || '.' || QUOTE_IDENT(t.TABLE_NAME))::bigint AS index_length, c.reltuples, obj_description(c.oid) AS comment FROM "information_schema"."tables" AS t LEFT JOIN "pg_namespace" n ON t.table_schema = n.nspname LEFT JOIN "pg_class" c ON n.oid = c.relnamespace AND c.relname=t.table_name WHERE t."table_schema"='public';
charmquark's profile image charmquark posted 3 weeks ago Permalink

When I run the query mannually it shows the tables,

however why does it not show it ( in a structured format on the left of the screen )

ansgar's profile image ansgar posted 3 weeks ago Permalink

The result say clearly these tables live in "public", not in "pg_toast_temp_1" (the one you selected in the screenshot). So if you expand "public", you should see these, don't you?

charmquark's profile image charmquark posted 3 weeks ago Permalink

yes, I do.. but why is the look so different?

ansgar's profile image ansgar posted 3 weeks ago Permalink

That green icon says these are procedures/functions.

You can see them in the second query from the log panel:

SELECT "p"."proname", "p"."proargtypes" FROM "pg_catalog"."pg_namespace" AS "n"
JOIN "pg_catalog"."pg_proc" AS "p" ON "p"."pronamespace" = "n"."oid"
WHERE "n"."nspname"='public';
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
charmquark's profile image charmquark posted 3 weeks ago Permalink

Ah I see them... Description is there any way to group them like in pgadmin

Description

PS: thank you for your patience

ansgar's profile image ansgar posted 3 weeks ago Permalink

You can group objects by their type in HeidiSQL too. See the help page for how to do that.

charmquark's profile image charmquark posted 2 weeks ago Permalink

Ah I see, thank you, perhaps will end up doing that.

PS: you have an awesome tool. thank you for supporting and keeping it free

Please login to leave a reply, or register at first.