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 02:22:00
Message-ID: 2601067.1734488520@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:
> Our database consists of 408032 blobs (pg_largeobject).
> Backup was made using zstd and it weights 70GB.
> While restoring the used memory increases constantly (from 5 MB to 5GB - i have got 8GB RAM, after reaching 5GB it uses 5GB for some time, maybe swaping) and then crashes with the error.

Yeah, leak reproduced here. Apparently it's specific to the zstd
code path, because I don't see it with the default compression
method. Should be easy to fix (awaiting valgrind results),
but in the meantime just use default compression.

Thanks for the report!

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomasz Szypowski 2024-12-18 07:12:06 RE: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
Previous Message Tom Lane 2024-12-18 01:40:21 Re: Surprising SeqScan of appendRel that can't contribute any rows to the result