Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Special care for partitioned tables #69

Open
allipatev opened this issue Jun 22, 2023 · 0 comments
Open

Feature: Special care for partitioned tables #69

allipatev opened this issue Jun 22, 2023 · 0 comments
Labels
feature Product feature

Comments

@allipatev
Copy link
Contributor

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.

@kaklakariada kaklakariada added the feature Product feature label Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Product feature
Projects
None yet
Development

No branches or pull requests

2 participants