The gadget spec URL could not be found
pg_default is the default resource queue created when you install the greenplum database. pg_default resource queue has an active statement limit of 20, no cost limit, no memory limit, and a medium priority setting. sachi=# select * from pg_catalog.pg_resqueue where rsqname='pg_default'; rsqname | rsqcountlimit | rsqcostlimit | rsqovercommit | rsqignorecostlimit ------------+---------------+--------------+---------------+-------------------- pg_default | 20 | -1 | f | 0 (1 row) The gadget spec URL could not be found or sachi=# select * from pg_catalog.pg_resqueue_attributes where rsqname='pg_default'; rsqname | resname | ressetting | restypid ------------+-------------------+------------+---------- pg_default | active_statements | 20 | 1 pg_default | max_cost | -1 | 2 pg_default | min_cost | 0 | 3 pg_default | cost_overcommit | 0 | 4 pg_default | priority | medium | 5 pg_default | memory_limit | -1 | 6 (6 rows) sachi=# All users must be assigned to a resource queue. If not explicitly assigned to a particular queue, users will go into the default resource queue, pg_default. If you wish to remove a role from a resource queue and put them in the default queue, change the role’s queue assignment to none. For example: sachi=# ALTER ROLE sachi RESOURCE QUEUE none; The gadget spec URL could not be found | If roles(users) are not explicitly assigned to a resource queue, they will go to the default resource queue. The gadget spec URL could not be found |
Resource scheduling is enabled by default when you install Greenplum Database. All database roles must be assigned to a resource queue. If an administrator creates a role without explicitly assigning it to a resource queue, the role is assigned to the default resource queue, pg_default.
