> Indexes seem bloated. Totally agree, you should organise re-indexes starting from the biggest.
> relation | size > -----------------------------------------+--------- > public.idx_catalog_resources_tags_gin | 117 GB > public.idx_catalog_resources_tags | 96 GB > public.idx_catalog_resources_resource | 39 GB > public.idx_catalog_resources_catalog | 39 GB > public.idx_catalog_resources_type_title | 34 GB > public.catalog_resources_pkey | 32 GB > public.idx_catalog_resources_type | 16 GB > public.catalog_resources | 9454 MB > public.edges_pkey | 2460 MB > public.edges | 875 MB > public.idx_certname_facts_name | 447 MB > public.certname_facts_pkey | 77 MB > public.idx_certname_facts_certname | 66 MB > public.resource_params | 66 MB > public.idx_resources_params_name | 60 MB > public.idx_resources_params_resource | 50 MB > public.resource_params_pkey | 43 MB > public.certname_facts | 41 MB > pg_toast.pg_toast_16463 | 34 MB > pg_toast.pg_toast_16463_index | 2360 kB So the index 'idx_catalog_resources_tags' was removed in 1.1.0 I think, so that is no longer needed. This points back to making sure you schema matches exactly what a known good 1.1.1 has, as things have been missed obviously. Try this tool out: http://www.apgdiff.com/diff_online.php I've got a pg_dump of a good 1.1.1 here: https://gist.github.com/kbarber/5104169 All you need to do is perform a pg_dump of your schema: pg_dump --schema-only puppetdb And use that online tool to compare your schema with the one I've provided. I would obviously double check its accuracy before doing anything drastic, but this should help to get your schema inline with what it should be. If you are paranoid about any part of the diff, paste the results in a gist and we can discuss it. > Lines: > > certname_facts 336426 > catalogs 2963 > resource_events 0 > reports 0 > certnames 2825 > certname_catalogs 2810 > certname_facts_metadata 2764 > catalog_resources 1881888 > resource_params 348806 > edges 3454907 > schema_migrations 9 None of this seems out of the ordinary. >> This should be evident in your puppetdb.log if you trace the uuid of a >> command. If commands 'fail' completely, they end up in the DQL located >> here: >> >> /var/lib/puppetdb/mq/discarded/ > > > Just looked at that directory, no entry with a recent date, so I guess they > go through eventually. Okay, well - lets at least get your schema back inline with what it should be, get your re-indexes done and we can come back round to this problem if it still exists. ken. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
