Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
Date
Msg-id 2601067.1734488520@sss.pgh.pa.us
Whole thread Raw
In response to Not able to restore database - error: could not decompress data: Allocation error : not enough memory  (Tomasz Szypowski <tomasz.szypowski@asseco.pl>)
Responses RE: Not able to restore database - error: could not decompress data: Allocation error : not enough memory
List pgsql-bugs
Tree view 
Tomasz Szypowski <tomasz.szypowski@asseco.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
uses5GB 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

pgsql-bugs by date:

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