Jira (PDB-5559) Ensure partition drops and migrations can eliminate all competitors

[Rob Browning (Jira)]

Title: Message Title

Rob Browning updated an issue   PuppetDB / PDB-5559 Ensure partition drops and migrations can eliminate all competitors Change By: Rob Browning Release Notes: Bug Fix Release Notes Summary: Make sure that partition drops and migration The coordination of report-related garbage collection has been improved.  Previously, if a separate `read-database` user were configured, incoming queries could block the garbage collection.  Whenever a separate `read-database` user *is* specified, the normal (write) database user must have the rights right to and always do terminate both the read and write users user's queries .   See   The [recommended configuration]({{puppetdb}}/configure_postgres.html) has been updated to include a suitable `grant puppetdb_read to puppetdb`. The coordination of migrations has also been improved.  Previously if a separate `read-database` user were configured, it wouldn't actually be evicted during migrations.  Note that the commit messages migrator user (role) must have the ability to terminate the read user's connections.  The [recommended configuration]({{puppetdb}}/configure_postgres.html) accomplishes this by granting the write user's role to the migrator via the `grant puppetdb to puppetdb_migrator` , doc changes which allows the migrator to terminate the read user's connections indirectly via the write user's membership in the read user's role , and release notes for additional information as described above . Add Comment   This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.474923.1668702253000.62596.1669919640049%40Atlassian.JIRA.