got exception when using databaseMetaData.getTables

Hi,

From your output:

[Vertica][VJDBC]Detail: Total allocated memory (MiB) = 1024.007 is about to exceed limit imposed by MaxParsedQuerySizeMB (MiB) = 1024.000

Looks like the request exceeded the "Maximum amount of memory allowed for parsing a single request" as determined by the MaxParsedQuerySizeMB parameter, but just by a little.

Try increasing the MaxParsedQuerySizeMB parameter for your DB.

Example

(My DB is named test_db):

dbadmin=> \x
Expanded display is on.

dbadmin=> SELECT parameter_name, current_value, description FROM vs_configuration_parameters WHERE parameter_name = 'MaxParsedQuerySizeMB';
-[ RECORD 1 ]--+--------------------------------------------------------------------------------------------------------------------------------------
parameter_name | MaxParsedQuerySizeMB
current_value  | 1024
description    | Maximum amount of memory allowed for parsing a single request; Increasing this value may help with 'Request size too big' errors (MB)

dbadmin=> ALTER DATABASE test_db SET MaxParsedQuerySizeMB = 1025;
ALTER DATABASE

dbadmin=> SELECT parameter_name, current_value, description FROM vs_configuration_parameters WHERE parameter_name = 'MaxParsedQuerySizeMB';
-[ RECORD 1 ]--+--------------------------------------------------------------------------------------------------------------------------------------
parameter_name | MaxParsedQuerySizeMB
current_value  | 1025
description    | Maximum amount of memory allowed for parsing a single request; Increasing this value may help with 'Request size too big' errors (MB)

Hello!
I have the same problem
Every hour we save new records from query_requests and dc_projection_used to a regular table. And then we make extracts from the table for technical analysis.
Everything worked fine for over a year (9.0, 9.1), but after upgrading to 9.2 there was a problem.
If the incremental extract contains more than 200k-400k records, then this leads to problems with the MaxParsedQuerySizeMB value = 1 GB

select start_timestamp, request, ... from projection_used where start_timestamp > '...'
ERROR 8617:  Request size too big
DETAIL:  Total allocated memory (MiB) = 1024.006 is about to exceed limit imposed by MaxParsedQuerySizeMB (MiB) = 1024.000

Column "request" has the type varchar (64000)

I tried to increase the value, but with a large interval of data (29M records) this stops helping even with 16GB