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 1tVG1l-006okV-Eu for pgsql-announce@arkaria.postgresql.org; Tue, 07 Jan 2025 20:18:14 +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 1tVG1j-007kdG-NY for pgsql-announce@arkaria.postgresql.org; Tue, 07 Jan 2025 20:18:11 +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 1tVG1i-007kd3-Qf for pgsql-announce@lists.postgresql.org; Tue, 07 Jan 2025 20:18:10 +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.96) (envelope-from ) id 1tVG1f-000Oxk-0X for pgsql-announce@lists.postgresql.org; Tue, 07 Jan 2025 20:18:10 +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=7G7WOYITOvcp5sMl0v9ly/gu38r8Xl13xKdKvukfGrU=; b=M2VrMul1ZP5B3RBlrVwEoT5LzA 428CKsXmhJSxGO223a1QYwVj/REgIx6Ipx+GqeZw+seZoIn8AOtitif4q0NnUfL+prBqcT0Ke3cJT DTXPqcWJDVueGkM22abWoSG2ufwz3YPwRLj+guAiWFO8IzbDhq6tpMZ8NVAJOp2yzILL0Ffi+cmF3 n3ldH8O9EcN6f0iVqTnn+fzmcH5pUE/zoQWx5qGIKVE0eQB8Mtb5hHQCU9Lo8QkPcfIiKdwkeL9J4 cfEDtP69UkTKmuGIgJAJma/395C8IOHj99aH5xL8j8VY6BR4E8b9zeIvBSV38QkP5QuPsng+q4MCQ 0kZgqLLA==; Received: from wrigleys.postgresql.org ([217.196.149.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 1tVG1d-001ALG-56 for pgsql-announce@lists.postgresql.org; Tue, 07 Jan 2025 20:18: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 1tVG1a-003n8g-Jo for pgsql-announce@lists.postgresql.org; Tue, 07 Jan 2025 20:18:02 +0000 Content-Type: multipart/mixed; boundary="===============5254425195263144334==" MIME-Version: 1.0 Subject: pg_partman 5.2.4 released To: PostgreSQL Announce From: Crunchy Data via PostgreSQL Announce Reply-To: news@crunchydata.com Date: Tue, 07 Jan 2025 20:17:28 +0000 Message-ID: <173628104842.818647.202629578334557073@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 2c2a5294c83334707257eb7358883198c3d651687a58a4803617106345bf6b9b List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============5254425195263144334== Content-Type: multipart/alternative; boundary="===============3450287568129774690==" MIME-Version: 1.0 --===============3450287568129774690== 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.2.4. Highlights of the version 5.2 release: * Support UUIDv7 and other custom encoded methods of time-based partitioni= ng. This allows a texted based partition column to be used as long as the v= alue can also be encoded to some time-based value. * Removed superuser requirement for installation. * Improved maintenance performance. * Fixed issues with BIGINT data type when using LIST partitioning. Further changes and bug fixes can be found in the [CHANGELOG](https://githu= b.com/pgpartman/pg_partman/blob/development/CHANGELOG.md). 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](https://github.com/pgpartman/pg_partman/issues) or [= pull requests](https://github.com/pgpartman/pg_partman/pulls) for any issue= s encountered. General questions can be submitted to [discussions](https://= github.com/pgpartman/pg_partman/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/development/d= oc/pg_partman.md](https://github.com/pgpartman/pg_partman/blob/development/= doc/pg_partman.md) Release Notes - [https://github.com/pgpartman/pg_partman/blob/development/C= HANGELOG.md](https://github.com/pgpartman/pg_partman/blob/development/CHANG= ELOG.md) Crunchy Data - [https://www.crunchydata.com](https://www.crunchydata.com) Crunchy Data is proud to support the development and maintenance of pg_part= man. --===============3450287568129774690== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_partman 5.2.4 released
 

pg_partman 5.2.4 released

Crunchy Data is proud to announce the relea= se of pg_partman 5.2.4.

Highlights of the version 5.2 release:

  • Support UUIDv7 = and other custom encoded methods of time-based partitioning. This allows a = texted based partition column to be used as long as the value can also be e= ncoded to some time-based value.
  • Removed superus= er requirement for installation.
  • Improved mainte= nance performance.
  • Fixed issues wi= th BIGINT data type when using LIST partitioning.

Further changes and bug fixes can be found = in the CHANGELO= G.

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 any 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_partm= an/blob/development/doc/pg_partman.md

Release Notes - https://github.com/pgpartman/pg_partman/bl= ob/development/CHANGELOG.md

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/.
 
--===============3450287568129774690==-- --===============5254425195263144334==--