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 1tbhpe-00Cj9u-Dd for pgsql-announce@arkaria.postgresql.org; Sat, 25 Jan 2025 15:12:22 +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 1tbhpc-003HHs-Gb for pgsql-announce@arkaria.postgresql.org; Sat, 25 Jan 2025 15:12:20 +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 1tbhmY-0034Fi-2D for pgsql-announce@lists.postgresql.org; Sat, 25 Jan 2025 15:09: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 1tbhmU-001SWB-1N for pgsql-announce@lists.postgresql.org; Sat, 25 Jan 2025 15:09:09 +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=PnbA3A87z+hV+rrM3ALw0LJS41WCNdzitIidbOxxD1I=; b=zW4c0rxDdI//f7qK3kJdZsqPy5 fDSCGDc65STavkaNZ9HG2iGIr0rIIJwseCvjqeBL0tV1gcH8BDGVIid1yfkMrhc4LVQHrwj0d7rh5 aPkGhf5g+xVYvBfOddc3/yL0td6lzHdmw1BHBIMZOgqok+dnCkoLOJy31iQF87hZwLXIqCFYqcBOd az/AYHJ3onGrReJEtVIQQ3i1Xf1+flRfhR9/GXqg83KHwZp3xir+JkXpYfZO346mLmQ0LY3NQcSSI U8kMfENUKcpPPmBhR0Ius38xmNplcGbV9WxyI0adukQx1K1d+1iUtD1irfLmzUEDhm0c2bv5wf1+o do6Uhqdg==; 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 1tbhmT-00ATzA-4F for pgsql-announce@lists.postgresql.org; Sat, 25 Jan 2025 15:09: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 1tbhmR-0061kn-KL for pgsql-announce@lists.postgresql.org; Sat, 25 Jan 2025 15:09:03 +0000 Content-Type: multipart/mixed; boundary="===============6205353150560743456==" MIME-Version: 1.0 Subject: pg_squeeze 1.8 released To: PostgreSQL Announce From: CYBERTEC PostgreSQL International GmbH via PostgreSQL Announce Reply-To: ah@cybertec.at Date: Sat, 25 Jan 2025 15:08:48 +0000 Message-ID: <173781772891.1065.786512603549159164@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 131f61dd6df51f46f0b302eb20e09635bdd79871937b19e99791ce0b61acff45 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6205353150560743456== Content-Type: multipart/alternative; boundary="===============4166358339208680397==" MIME-Version: 1.0 --===============4166358339208680397== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable This release fixes a bug in the `squeeze.squeeze_table()` function, which c= an now cause data corruption. The problem can occur if other clients run DDL statements or squeeze other tables around the time the function starts its execution. Squeezing launched by the scheduler worker (as described in the "Register table for regular processing" section of [README](https://github.com/cybert= ec-postgresql/pg_squeeze/blob/REL1_8/README.md)) is not affected. The bug is only present in pg_squeeze 1.7. Please upgrade to version 1.8 as= soon as possible. Source code is available [here](https://github.com/cybertec-postgresql/pg_s= queeze/releases/tag/REL1_8_0). Binaries should be available in the [PostgreSQL repositories](https://www.p= ostgresql.org/download/) pretty soon. --===============4166358339208680397== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_squeeze 1.8 released
 

pg_squeeze 1.8 released

This release fixes a bug in the squee= ze.squeeze_table() function, which can now cause data corruption. The problem can occur if other clients run DDL statements or squeeze other tables around the time the function starts its execution.

Squeezing launched by the scheduler worker = (as described in the "Register table for regular processing" section of README) is not affected.

The bug is only present in pg_squeeze 1.7. = Please upgrade to version 1.8 as soon as possible.

Source code is available here.

Binaries should be available in the PostgreSQL repositories pretty soon.
This email was sent to you from CYBERTEC PostgreSQL International GmbH. It = was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to CYBERTEC PostgreSQL International GmbH.

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/.
 
--===============4166358339208680397==-- --===============6205353150560743456==--