pg_partman 5.0.0-beta available for community testing

Crunchy Data is proud to announce the upcoming release of pg_partman 5.0.0. We are currently releasing a beta version for community testing.

### Highlights of this release

Version 5.0.0-beta August 16th, 2023

- pg_partman is deprecating many older features. These are breaking changes, so please proceed with caution on updates
- Removing trigger-based partitioning
- Special time-based intervals are removed
- A minimum version of PostgreSQL 14 is required
- The default table is optional
- Simplified partitioning suffixes

The top of the update file contains the current [full release notes](https://github.com/pgpartman/pg_partman/blob/5.0.0-beta/updates/pg_partman--4.7.3--5.0.0-beta.sql).

Since this is a beta release, this version cannot be installed directly. The standard installation procedures will install the latest stable release (4.7.3) into the database. To install 5.0.0-beta, you will then have to run an extension update

```
ALTER EXTENSION pg_partman UPDATE TO '5.0.0-beta’;
```

There will also not be any upgrade paths from 5.0.0-beta to the final 5.0.0. So please do not install this for production use.

Special instructions for certain upgrade scenarios can be found in the [5.0.0 upgrade guide](https://github.com/pgpartman/pg_partman/blob/5.0.0-beta/doc/pg_partman_5.0.0_upgrade.md). General usage instructions and other guides can be found in the [documents folder](https://github.com/pgpartman/pg_partman/blob/5.0.0-beta/README.md#documentation) of the 5.0.0-beta branch.

### About pg_partman
[https://github.com/pgpartman/pg_partman](https://github.com/pgpartman/pg_partman)

pg_partman is an extension to create and manage both time-based and number-based table partition sets. As of version 5.0.0, only built-in, declarative partitioning is supported and the older trigger-based methods have been deprecated.

The declarative partitioning built into PostgreSQL provides the commands to create a partitioned table and its children, but it does not provide a means of automating that child table maintenance over time (Ex. adding new children, dropping old ones based on a retention policy). It also does not provide a means to easily turn an existing table into a partitioned table or vice versa. pg_partman aims to use the built-in declarative features that PostgreSQL provides, but build upon them to provide those missing features as well as many others to help make managing partitions easier.

**Thank you in advance for helping with the testing of pg_partman’s upcoming release. Please submit [issues](https://github.com/pgpartman/pg_partman/issues) or [pull requests](https://github.com/pgpartman/pg_partman/pulls) for anything you find. General questions can be submitted to [discussions](https://github.com/pgpartman/pg_partman/discussions).**