Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomasz Szypowski <tomasz(dot)szypowski(at)asseco(dot)pl>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
Date: 2024-12-18 15:13:04
Message-ID: 2770310.1734534784@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tomasz Szypowski <tomasz(dot)szypowski(at)asseco(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2024-12-19 02:45:47 Re: Build failure with GCC 15 (defaults to -std=gnu23)
Previous Message Laurenz Albe 2024-12-18 14:25:40 Re: Incompatibility of newest pg_restore with PostgreSQL-Servers older or equal to version 16