Re: [PATCHES] Remove FATAL from pg_lzdecompress

2008-04-10 Thread Zdenek Kotala
Tom Lane napsal(a): Zdenek Kotala [EMAIL PROTECTED] writes: I attach patch which adds boundaries check and memory overwriting protection when compressed data are corrupted. Good point. Is there plan to applied also on other branch? I wasn't planning to back-patch it. Given the lack of

Re: [PATCHES] Remove FATAL from pg_lzdecompress

2008-03-11 Thread Zdenek Kotala
Tom Lane napsal(a): Zdenek Kotala [EMAIL PROTECTED] writes: I attach patch which adds boundaries check and memory overwriting protection when compressed data are corrupted. Applied with revisions --- it appeared to me that it got the corner case wrong where we find a tag just at the end of

Re: [PATCHES] Remove FATAL from pg_lzdecompress

2008-03-11 Thread Tom Lane
Zdenek Kotala [EMAIL PROTECTED] writes: I attach patch which adds boundaries check and memory overwriting protection when compressed data are corrupted. Good point. Is there plan to applied also on other branch? I wasn't planning to back-patch it. Given the lack of field reports of

Re: [PATCHES] Remove FATAL from pg_lzdecompress

2008-03-07 Thread Tom Lane
Zdenek Kotala [EMAIL PROTECTED] writes: I attach patch which adds boundaries check and memory overwriting protection when compressed data are corrupted. Applied with revisions --- it appeared to me that it got the corner case wrong where we find a tag just at the end of the input but there's

Re: [PATCHES] Remove FATAL from pg_lzdecompress

2008-03-03 Thread Bruce Momjian
Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches It will be applied as soon as one of the PostgreSQL committers reviews and approves it. ---

[PATCHES] Remove FATAL from pg_lzdecompress

2008-02-29 Thread Zdenek Kotala
I attach patch which adds boundaries check and memory overwriting protection when compressed data are corrupted. Current behavior let code overwrite a memory and after that check if unpacked size is same as expected value. In this case elog execution fails (at least on Solaris - malloc has