Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rtEnU-00DN4H-P4 for pgsql-announce@arkaria.postgresql.org; Sat, 06 Apr 2024 22:46:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rtEnT-000STH-Fp for pgsql-announce@arkaria.postgresql.org; Sat, 06 Apr 2024 22:46:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rtElk-0004Nv-13 for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44:16 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rtElb-001AmF-4z for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=GuymTMCKzzp84hlv3v0s22uVkVDz/yRq+3Qsrrs0mcY=; b=afAeCul8tJsmceXePiq5g4x8wK BrnyztoL9RAIKsIAfkT5NV1kNuyZ8WwEgPfiLiKxR1zH6F8ePWV5IzpMR2HsM9rQjfOClSBIy1fBR OH7lZx4i7EIySnje6i73ed4x579IAgb3pFbvqypvam3/CvKE2otm3uO0LD8l7SBk2AJgAJGgrB0nD REyT1RdxIn7iJuWnFwmQPevF+0s7WZ7AAG2AqEp7RJv6F0dA5ohOCRZFsTyqyq/Cta2ESWh/7Ly+4 Z209y+Mx4ujGINLtCdY2j16msBtWrpn1QaqjDDG5pOxecQnHSsOb0n7nSnIDC3N1CjCkTy1Rhujja v6JhX3kw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rtElZ-002dfX-6N for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rtElW-00ADFi-RX for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44:03 +0000 Content-Type: multipart/mixed; boundary="===============4551932976357557081==" MIME-Version: 1.0 Subject: pg_partman 5.1.0 & 4.8.0 released To: PostgreSQL Announce From: Crunchy Data via PostgreSQL Announce Reply-To: news@crunchydata.com Date: Sat, 06 Apr 2024 22:43:25 +0000 Message-ID: <171244340515.683.5132146684622534011@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: b8f61dfcf52328fd1ad630c25f1e40ed541e7b0c2a9f63652b25743f84e9a660 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============4551932976357557081== Content-Type: multipart/alternative; boundary="===============3017518726585799422==" MIME-Version: 1.0 --===============3017518726585799422== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Crunchy Data is proud to announce the release of pg_partman 5.1.0 & 4.8.0. Highlights of this release Version 5.1.0 April 2, 2024 * Support LIST partitioning for single value integers. * EXPERIMENTAL support for partitioning based on numeric values * Allow explicit ordering of partition set maintenance * Properly inherit tablespaces Further changes and bug fixes can be found in the CHANGELOG=20 Version 4.8.0 * Fix the partition_gap_fill() function to allow skipping the analyze ste= p. Note this is not an option in 5.x since the analyze step was refactored = and never runs automatically during a call to the gap fill function anymore. * Note that there is no way to directly install version 4.8.0. A prior ver= sion must be installed first and then upgraded to 4.8.0. It is recommended = that you migrate to the latest major version for continued support of pg_pa= rtman. About 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 de= precated. The declarative partitioning built into PostgreSQL provides the commands to= create a partitioned table and its children, but it does not provide a mea= ns of automating that child table maintenance over time (Ex. adding new chi= ldren, dropping old ones based on a retention policy). It also does not pro= vide a means to easily turn an existing table into a partitioned table or v= ice versa. pg_partman aims to use the built-in declarative features that Po= stgreSQL provides, but build upon them to provide those missing features as= well as many others to help make managing partitions easier. Please submit issues or pull requests for any issues encountered. General q= uestions can be submitted to discussions. Links: Website - [https://github.com/pgpartman/pg_partman](https://github.com/pgpa= rtman/pg_partman) Installation - [https://github.com/pgpartman/pg_partman#installation](https= ://github.com/pgpartman/pg_partman#installation) Documentation - [https://github.com/pgpartman/pg_partman/blob/master/doc/pg= _partman.md](https://github.com/pgpartman/pg_partman/blob/master/doc/pg_par= tman.md) Release Notes - [https://github.com/pgpartman/pg_partman/blob/master/CHANGE= LOG.txt](https://github.com/pgpartman/pg_partman/blob/master/CHANGELOG.txt) Crunchy Data - [https://www.crunchydata.com](https://www.crunchydata.com) Crunchy Data is proud to support the development and maintenance of pg_part= man. --===============3017518726585799422== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_partman 5.1.0 & 4.8.0 released
 

pg_partman 5.1.0 & 4.8.0 released

Crunchy Data is proud to announce the relea= se of pg_partman 5.1.0 & 4.8.0.

Highlights of this release

Version 5.1.0 April 2, 2024

  • Support LIST pa= rtitioning for single value integers.
  • EXPERIMENTAL su= pport for partitioning based on numeric values
  • Allow explicit = ordering of partition set maintenance
  • Properly inheri= t tablespaces

Further changes and bug fixes can be found = in the CHANGELOG

Version 4.8.0

  • Fix the partiti= on_gap_fill() function to allow skipping the analyze step. Note this is not= an option in 5.x since the analyze step was refactored and never runs auto= matically during a call to the gap fill function anymore.
  • Note that there= is no way to directly install version 4.8.0. A prior version must be insta= lled first and then upgraded to 4.8.0. It is recommended that you migrate t= o the latest major version for continued support of pg_partman.

About pg_partman

pg_partman is an extension to create and ma= nage 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 tr= igger-based methods have been deprecated.

The declarative partitioning built into Pos= tgreSQL provides the commands to create a partitioned table and its childre= n, but it does not provide a means of automating that child table maintenan= ce over time (Ex. adding new children, dropping old ones based on a retenti= on policy). It also does not provide a means to easily turn an existing tab= le 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 p= rovide those missing features as well as many others to help make managing = partitions easier.

Please submit issues or pull requests for a= ny issues encountered. General questions can be submitted to discussions.

Links:

Website - htt= ps://github.com/pgpartman/pg_partman

Installation - https://github.com/pgpartman/pg_partman#installation

Documentation - https://github.com/pgpartman/pg_partman/bl= ob/master/doc/pg_partman.md

Release Notes - https://github.com/pgpartman/pg_partman/blob/m= aster/CHANGELOG.txt

Crunchy Data - https://ww= w.crunchydata.com

Crunchy Data is proud to support the develo= pment and maintenance of pg_partman.
This email was sent to you from Crunchy Data. It was delivered on their beh= alf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Crunchy Data.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============3017518726585799422==-- --===============4551932976357557081==--