pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomasz Szypowski <tomasz.szypowski@asseco.pl>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
Date: Wed, 18 Dec 2024 10:13:04 -0500
Message-ID: <2770310.1734534784@sss.pgh.pa.us> (raw)
In-Reply-To: <DU0PR04MB94191A580B07749939AE500799052@DU0PR04MB9419.eurprd04.prod.outlook.com>
References: <DU0PR04MB94193D038A128EF989F922D199042@DU0PR04MB9419.eurprd04.prod.outlook.com>
	<2601067.1734488520@sss.pgh.pa.us>
	<DU0PR04MB94191A580B07749939AE500799052@DU0PR04MB9419.eurprd04.prod.outlook.com>

Tomasz Szypowski <tomasz.szypowski@asseco.pl> writes:
> Do you think it will be fixed within few months? Next year we plan to upgrade our clients to 17 and zstd compression is about two times faster than gzip and produces about 20% less backup.

The fix will be in February's releases.

			regards, tom lane

view thread (4+ messages)

Message-ID: <2770310.1734534784@sss.pgh.pa.us>
Permalink:  ../2770310.1734534784@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2770310.1734534784@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, tomasz.szypowski@asseco.pl, pgsql-bugs@lists.postgresql.org
  Subject: Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
  In-Reply-To: <2770310.1734534784@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox