Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I attached backported pg_lzcompress patch which is already in head for version 8.2 and 8.3.

Version 8.1 and prior contains more changes in decompress code and they does not contain any check. Shell I backported it as well or it will be better to keep it untouched?

AFAICS the only nontrivial patch in pg_lzcompress.c between 7.4 and 8.2
is my cleanup patch here:
That's been in the tree long enough that I wouldn't have any hesitation
about back-porting it, so that all the supported versions would have
the same lzcompress code.

OK I will backport your and my patch together back to the 7.4.

About the only reason I can see not to do it
is that conceivably some third-party code somewhere might be calling
pglz_compress directly; in which case an API change in a minor release
would be a problem for them.

Hmm, It brings me idea that we should have some stable API definition for C function. For example API for datatype helps to upgrade user datatypes without any changes (no recompilation). The same model uses e.g. Solaris for driver. Binary drivers are compatible and drivers from S8 should work on S10.

On the other hand, I remain unconvinced that this problem is severe
enough to justify much backporting work.  AFAIK we've only seen one
occurence of a problem to date.

I know about two occurrence. One was reported on -bug (
and second was reported from our customer.

The main problem is that you are not able to fix corrupted data. When database raise error on damaged data you are able to catch this error and remove affected row. If database crashes than only gdb guru is able to mine ctid of affected row or any other row specification from core dump.


Sent via pgsql-patches mailing list (
To make changes to your subscription:

Reply via email to