Tom Lane <t...@sss.pgh.pa.us> wrote: > Another not-exactly-trivial requirement is to figure out how to > not break on-disk compatibility when installing an alternative > compression scheme. In hindsight it might've been a good idea if > pglz_compress had wasted a little bit of space on some sort of > version identifier ... but it didn't. Doesn't it always start with a header of two int32 values where the first must be smaller than the second? That seems like enough to get traction for an identifiably different header for an alternative compression technique. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
