Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow PDB-5554 intended to improve performance around partition remove by making use of `alter table detach partition concurrently`. But that can only be used with declarative partitions and our partitions are inheritance based.Migrate resource_events and reports partitioning to [declarative partitions|https://www.postgresql.org/docs/current/ddl-partitioning.html].[https://www.2ndquadrant.com/en/blog/how-to-migrate-from-inheritance-based-partitioning-to-declarative-partitioning-in-postgresql/] is one example.Need to validate that this migration won't have a significant impact on larger databases with a significant number of reports and events.NOTE: * The minimum PostgreSQL version is now 11 with these migrations. * Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow PDB-5554 intended to improve performance around partition remove by making use of `alter table detach partition concurrently`. But that can only be used with declarative partitions and our partitions are inheritance based.Migrate resource_events and reports partitioning to [declarative partitions|https://www.postgresql.org/docs/current/ddl-partitioning.html].[https://www.2ndquadrant.com/en/blog/how-to-migrate-from-inheritance-based-partitioning-to-declarative-partitioning-in-postgresql/] is one example.Need to validate that this migration won't have a significant impact on larger databases with a significant number of reports and events. NOTE: The minimum PostgreSQL version is now 11 with these migrations. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- You received this
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5567 Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Change By: Joshua Partlow Release Notes: Enhancement Release Notes Summary: The reports and resource_events tables were migrated to use PostgreSQL declarative partitioning in support of PDB-5554.This changes requires a minimum of PostgreSQL 11. 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.475715.1669757045000.7707.1675469700043%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Joshua Partlow Labels: docs 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.472748.1666300333000.7706.1675469520027%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow updated an issue PuppetDB / PDB-5554 Remove partitions in a non-world-blocking way Change By: Joshua Partlow Release Notes: Enhancement Release Notes Summary: PuppetDB installations with PostgreSQL 14+ will detach reports and resource_events partitions concurrently before dropping them. 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.472748.1666300333000.7705.1675469460026%40Atlassian.JIRA.
Jira (PDB-5567) Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions
Title: Message Title Joshua Partlow commented on PDB-5567 Re: Migrate PDB reports and resource_events inheritance based partitions to postgresql declarative partitions Charlie Sharpsteen this is the migration ticket supporting PDB-5554 I pinged you about. 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.475715.1669757045000.7704.1675469400093%40Atlassian.JIRA.
Jira (PDB-5554) Remove partitions in a non-world-blocking way
Title: Message Title Joshua Partlow commented on PDB-5554 Re: Remove partitions in a non-world-blocking way Charlie Sharpsteen this pdb change will be going into 7.x and 8.x/main and makes an adjustment to gc, but only if you are running PG14+. This allows us to detach the tables with reduced locking before dropping them. The PG11 workflow should be unchanged. However this required adjusting the reports and resource_events tables and their partitions to use postgresql declarative partitioning instead of the older inheritance partitioning available in PG10. That's PDB-5567. That also locked in pdb postgresql requirements to PG11 as a minimum. PR is open here if you want to review it. 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.472748.1666300333000.7702.1675469340022%40Atlassian.JIRA.
Jira (PDB-5589) Investigate pdb upgrade times with migration 81/82
Title: Message Title Joshua Partlow created an issue PuppetDB / PDB-5589 Investigate pdb upgrade times with migration 81/82 Issue Type: Task Assignee: Unassigned Components: PuppetDB, PuppetDB Enterprise Created: 2023/02/03 3:59 PM Priority: Normal Reporter: Joshua Partlow Double check how much time the index regeneration from pdb migrations 81/82 takes (these migrations rejigger the reports/resource_events partitions to use declarative partitioning). Time to upgrade In versions of PG 11.17 the reports_noop_idx indexes generated on the child partitions is named differently than in 11.18 (for example, reports_20230130z_noop_idx instead of reports_noop_idx_20230130z, see: https://github.com/puppetlabs/puppetdb/pull/3748/commits/133c3771e84d8b389bb4eca74907f7b03a96e389). It would be good to validate what the indexes look like after upgrading on =11.18 (possibly easiest to test this with PE) Add Comment
Jira (PUP-11722) concurrent-ruby 1.2.0 breaks puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11722 concurrent-ruby 1.2.0 breaks puppet Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Updates puppet to be compatible with the concurrent-ruby gem versions 1.2 and 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.479492.1674507142000.7631.1675450080029%40Atlassian.JIRA.
Jira (FACT-3177) Update facter acceptance tests to handle puppet7 vs puppet8
Title: Message Title Christopher Thorn updated an issue Facter / FACT-3177 Update facter acceptance tests to handle puppet7 vs puppet8 Change By: Christopher Thorn Release Notes: Not Needed 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.479046.1673585982000.7598.1675446060100%40Atlassian.JIRA.
Jira (FACT-3170) Facter resolves facts multiple times when providers are confined based on facts, especially on Windows
Title: Message Title Christopher Thorn updated an issue Facter / FACT-3170 Facter resolves facts multiple times when providers are confined based on facts, especially on Windows Change By: Christopher Thorn Release Notes: Bug Fix Release Notes Summary: Facter 4 previously was not looking to use any cache information when looking up a fact or value Facter methods. We have resolved that to now use cache information when using the fact or value methods. 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.477181.1671137416000.7597.1675446060033%40Atlassian.JIRA.
Jira (FACT-3171) Facter incorrectly filter IPv6 link-local unicast addresses
Title: Message Title Christopher Thorn updated an issue Facter / FACT-3171 Facter incorrectly filter IPv6 link-local unicast addresses Github handle of user who contirbuted: smortex . 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.477767.1672454812000.7596.1675445820020%40Atlassian.JIRA.
Jira (FACT-3171) Facter incorrectly filter IPv6 link-local unicast addresses
Title: Message Title Christopher Thorn updated an issue Facter / FACT-3171 Facter incorrectly filter IPv6 link-local unicast addresses Change By: Christopher Thorn Fix Version/s: FACT 4.3.0 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.477767.1672454812000.7595.1675445700023%40Atlassian.JIRA.
