Start a new topic

postgresql 10 beta - partition table

PostgreSQL version 10(beta) supports partitioned tables.

Table attribute 'p' has been added.

The parent table is not visible.


It works after modifying as below.

      <Command id="postgresql8.getTables">
SELECT c.relname                                     AS "Name",
       n.nspname                                     AS "Schema",
       pg_get_userbyid(c.relowner)                   AS "Owner",
       t.spcname                                     AS "Tablespace",
       c.relhasindex                                 AS "Has Indexes",
       c.relhasrules                                 AS "Has Rules",
            <If test="#util.isDatabaseVersionGTE(8,4)">
       c.relhastriggers                               AS "Has Triggers",
       (c.reltriggers > 0)                            AS "Has Triggers",
       c.relisshared                                 AS "Is Shared",
       c.relnatts                                    AS "N Cols",
       pg_catalog.obj_description(c.oid, 'pg_class') AS "Comment"
FROM   pg_class c
   LEFT JOIN pg_namespace n   ON n.oid = c.relnamespace
   LEFT JOIN pg_tablespace t  ON t.oid = c.reltablespace
WHERE 1=1 
<If test="#util.isDatabaseVersionGTE(10,0)">
AND c.relkind in( 'r'::"char", 'p'::"char")
AND c.relkind in( 'r'::"char")
AND   n.nspname LIKE '${schema}'
AND   c.relname LIKE '${table}'
ORDER BY n.nspname, c.relname


Hi Wolfgang,

The issue with the empty Columns tab is due to the bundled JDBC driver version. It is fixed in the latest version, 42.2.1, available here:

We will look into bundling the latest driver version with the next maintenance release. If you want to upgrade now, create a new Driver Manager Entry for it e.g. named PostgreSQL 42.2.1 and select that driver for your connection, as described here:

I cannot reproduce the second issue as I said earlier so your input about what I may be missing is welcome.

Best Regards,


Hi Hans,

here is how I reproduce the second problem:

CREATE TABLE amk_schema.measurement (
    city_id         int not null,
    logdate         date not null,
    peaktemp        int,
    unitsales       int

CREATE TABLE amk_schema.measurement_01 PARTITION OF amk_schema.measurement
    FOR VALUES FROM ('2017-01-01') TO ('2018-01-01');
CREATE TABLE amk_schema.measurement_00 PARTITION OF amk_schema.measurement
    FOR VALUES FROM ('2016-01-01') TO ('2017-01-01');
insert into amk_schema.measurement (city_id, logdate, peaktemp, unitsales) values (17, '2017-05-04', 30, 100);

-- I even do that:
grant all on amk_schema.measurement to amk_schema;
grant all on amk_schema.measurement_01 to amk_schema;
grant all on amk_schema.measurement_00 to amk_schema;

After all, I am happy when I open the database as user "postgres", but when I open it as "amk_schema"

I only see the partitions "measurement_00" and "measurement_01" in the navigation pane. But not the

parent table "measurement".

Best regards,


Hi Wolfgang,

Strange. I'm still not able to reproduce this. I have tested creating the table and partitions both with postgres as the owner and with my test schema as the owner. In both cases, I see the table under the Tables nodes and its partitions under the Partitions node. My test schema, corresponding to your "ask_schema" is named "test" and I have also used this GRANT statement if that makes a difference:

grant all privileges on schema test to test

Please open Tools->Debug Window and enable debugging for DbVisualizer. Click on the garbage can button to remove old output. Then perform this operation again and include the debug output in your reply. 

I did find another bug, namely that the database qualifier in the DDL for the partitions is incorrectly set to the owner instead of the database. This will be fixed in the next maintenance release.

Best Regards,


 Hi Hans,

I have produced the debug log you wanted. See attachment.

The log protocols the following actions:

- connect to the database

- open the database navigation item (AMK173 in this case)

- open the "TABLES" item

But do not waste too much time on this - it's not urgent :)

Best regards



Hi Wolfgang,

I will look into this but I take your advice and leave it for later.

Best Regards,


Hi Wolfgang,

I finally had some time to look at this. There seems to be some configuration issues, because in your installation, a profile named /opt/DbVisualizer/resources/profiles/postgresql.xml is used, when it instead should use one named /opt/DbVisualizer/resources/profiles/postgresql8.xml (the difference being the "8" in the filename). The one that gets used in your case is a very limited one that is intended for PostgreSQL versions older than version 8. Have you manually changed anything in your DbVisualizer installation? Which installer did you use when you installed DbVisualizer 10.0.8?

The choice of profile is based in the database version returned by the JDBC driver. I see another oddity in your log that indicates that you may have the wrong driver installed, namely that it throws a java.sql.SQLFeatureNotSupportedException for the Statement#getLargeUpdateCount() method. The driver bundled with DbVisualizer does not do this. Have you replaced the driver that comes bundled with DbVisualizer?

If none of this sounds familiar, I suggest that you uninstall DbVisualizer and reinstall the latest version (10.0.10). It is important that you first uninstall the current version, to get rid of potentially old files that have not been replaced when upgrading. Reinstalling DbVisualizer does not affect any user settings.

Best Regards,



Just to inform you that the just released DbVisualizer 10.0.14 now fixes this that you reported a while ago:

- if you click on the partitioned table in the navigator, you can see the columns of the table in a tree view.

  But when you open this table in the database window (the big window on the right side), the "Columns"

  tab does not show the columns. No big deal, but this seems to be wrong ...



Hi Roger,

thank you very much!



Now that PostgreSQL supports multi-level partitions, would be nice if dbvis could export them.

I'm running dbvis 12.0.4 and when I do a table export ( only allowed at the highest level ), it only exports the first level partitions.



Login or Signup to post a comment