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
Per discussion in #804, Martin should warn users if PostgreSQL discovery step is taking too long.
For each PostgreSQL connection, e.g. in PgConfig::resolve, print a warning if table/function instantiation takes longer than 5 (?) seconds. This could probably be done using this method waiting for the instantiate_tables function. The instantiate_functions could also use some sort of a warning in case we implement retrieving a test tile, but it probably won't have the same message.
So, if instantiate_tables takes over 5 seconds, print something like this:
WARN: PostgreSQL table discovery is taking too long. Make sure your table geo columns have a GIS index, or use --disabling-bounds.
The text was updated successfully, but these errors were encountered:
Adds a warning message using the suggested implementation in #810.
Thanks for the recommended approach in the ticket! This one seemed
straightforward enough that local tests would do, which I ran by adding
a delay to `instantiate_tables`.
---------
Co-authored-by: Yuri Astrakhan <YuriAstrakhan@gmail.com>
Per discussion in #804, Martin should warn users if PostgreSQL discovery step is taking too long.
For each PostgreSQL connection, e.g. in
PgConfig::resolve
, print a warning if table/function instantiation takes longer than 5 (?) seconds. This could probably be done using this method waiting for theinstantiate_tables
function. Theinstantiate_functions
could also use some sort of a warning in case we implement retrieving a test tile, but it probably won't have the same message.So, if
instantiate_tables
takes over 5 seconds, print something like this:The text was updated successfully, but these errors were encountered: