customize the frequency of action log fetches

Hi and thanks for a fantastic product!

After turning on log_statement = 'all' on in the postgresql.conf on my local installation of PostgreSQL I noticed there are updates running every second to the hdb_catalog. I wonder if it that is expected?

This is what the log looks like:

2021-01-18 20:04:10.409 CET [61445] LOG:  execute 0: 
	      UPDATE hdb_catalog.event_log
	      SET locked = 't'
	      WHERE id IN ( SELECT l.id
	                    FROM hdb_catalog.event_log l
	                    WHERE l.delivered = 'f' and l.error = 'f' and l.locked = 'f'
	                          and (l.next_retry_at is NULL or l.next_retry_at <= now())
	                          and l.archived = 'f'
	                    ORDER BY created_at
	                    LIMIT $1
	                    FOR UPDATE SKIP LOCKED )
	      RETURNING id, schema_name, table_name, trigger_name, payload::json, tries, created_at
	      
2021-01-18 20:04:10.409 CET [61445] DETAIL:  parameters: $1 = '100'
2021-01-18 20:04:10.409 CET [61446] LOG:  execute <unnamed>: 
	        update hdb_catalog.hdb_action_log set status = 'processing'
	        where
	          id in (
	            select id from hdb_catalog.hdb_action_log
	            where status = 'created'
	            for update skip locked limit 10
	          )
	        returning
	          id, action_name, request_headers::json, session_variables::json, input_payload::json
	      
2021-01-18 20:04:11.418 CET [61446] LOG:  execute 0: 
	      UPDATE hdb_catalog.event_log
	      SET locked = 't'
	      WHERE id IN ( SELECT l.id
	                    FROM hdb_catalog.event_log l
	                    WHERE l.delivered = 'f' and l.error = 'f' and l.locked = 'f'
	                          and (l.next_retry_at is NULL or l.next_retry_at <= now())
	                          and l.archived = 'f'
	                    ORDER BY created_at
	                    LIMIT $1
	                    FOR UPDATE SKIP LOCKED )
	      RETURNING id, schema_name, table_name, trigger_name, payload::json, tries, created_at
	      
2021-01-18 20:04:11.418 CET [61446] DETAIL:  parameters: $1 = '100'
2021-01-18 20:04:11.419 CET [61445] LOG:  execute <unnamed>: 
	        update hdb_catalog.hdb_action_log set status = 'processing'
	        where
	          id in (
	            select id from hdb_catalog.hdb_action_log
	            where status = 'created'
	            for update skip locked limit 10
	          )
	        returning
	          id, action_name, request_headers::json, session_variables::json, input_payload::json

hdb_catalog.event_log and hdb_catalog.hdb_action_log are both empty.

I started out with version 1.1.0 about a year ago and have since upgraded to 1.3.3. I went straight from version 1.1.0 to 1.3.2 by just switching the version in the docker start command. And the same way I upgraded to from 1.3.2 to 1.3.3:

docker run -p 8080:8080 \
  -e HASURA_GRAPHQL_DATABASE_URL=postgres://username:password.docker.internal:5432/vb \
  -e HASURA_GRAPHQL_ENABLE_CONSOLE=true \
  hasura/graphql-engine:v1.3.3

My production version of Hasura in Kubernetes is still 1.1.0.

Thanks!

[tirumaraiselvan]

Released in v2.0.0-alpha.7 with the env var HASURA_GRAPHQL_ASYNC_ACTIONS_FETCH_INTERVAL (milliseconds)

[tirumaraiselvan]

But the event refetch is still run every second.

@xiaoyu-tamu This is WIP as well.