You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some partitioning mechanisms in PostgreSQL are implemented as a set of tables with corresponding triggers.
Because of it in fact creation of a partitioned table might end up in several other tables.
That's the case for the customer and they have so many partitions that they even get the error
The size of the list of the selected tables exceeded the default allowed maximum: 1000 Please, use the 'TABLE_FILTER' property to define the list of tables you need.
during Virtual Schema creation.
Obviously, tuning TABLE_FILTER or MAX_TABLE_COUNT parameters would solve the problem at hand.
However, a more elegant and reasonable solution is to add a parameter to PostgreSQL Virtual Schema to exclude tables that are a part of higher-level partitioned tables.
PostgreSQL JDBC driver might already have tooling for it: pgjdbc/pgjdbc#1708
Please consider researching this topic and implementing such functionality.
The text was updated successfully, but these errors were encountered:
Some partitioning mechanisms in PostgreSQL are implemented as a set of tables with corresponding triggers.
Because of it in fact creation of a partitioned table might end up in several other tables.
That's the case for the customer and they have so many partitions that they even get the error
during Virtual Schema creation.
Obviously, tuning TABLE_FILTER or MAX_TABLE_COUNT parameters would solve the problem at hand.
However, a more elegant and reasonable solution is to add a parameter to PostgreSQL Virtual Schema to exclude tables that are a part of higher-level partitioned tables.
PostgreSQL JDBC driver might already have tooling for it: pgjdbc/pgjdbc#1708
Please consider researching this topic and implementing such functionality.
The text was updated successfully, but these errors were encountered: