Following this out of curiosity. What is driving the need to use 32K pages? My understanding has always been that there's a little voodoo to tuning the page size, to balance storage efficiency vs. performance, and one of the key factors is record widths in the db. I.e., if the db is mostly little records, a larger page size may not provide much benefit.

In my database, in a separate table space, there is table with texts of documents of various formats (files with documents). Now the size of this table space is approximately 2 GB, taking into account a page of 16 KB, it can grow to 4 GB. I don’t want to store files with document texts outside the database (it’s not convenient).

I know about the algorithm (method) of how to programmatically split one table into several table spaces. But before putting it into operation, I first want to increase the size of the table space to its maximum size of 8 GB (in order to make full use of the maximum number of table space files in one database). And that’s why I need a 32 kb page.

I'm not talking about limiting the database file dependent on the file system, but about the limiting depending on the page size of the database.

Dbspace size = 2^28 x page size