Fixed Bug List for pg_lesslog V.1.4.1

   Contact: koichi_szk@gmail.com

1) Incorrect record length calculation for GISTxxx record.
2) BKP removal for 1) is not available now to prevent recovery problem.
   GiST does not assume XLOG_NOOP record can appear at any place.
3) Now pg_compresslog and pg_decompresslog can overwrite compressed and
   uncompressed XLOG segment respectively.  In previous version, it
   caused error, which is different from cp's behavior.
4) Added logging feature for pg_compresslog to dump the structure of
   original WAL segment.   To do this, you should set the environment
   LESSLOG_LOG to the path of the log file.   If you set LESSLOG_ARCHIVE
   to "a", log will be appended to the log file if exists.  Otherwise,
   it will overwrite the file.
5) Provide thorough test program of pg_compresslog and pg_decompresslog.
   So far, I'm not successful to test CLOG_TRUNCATE, XLOG_HEAP_INIT_PAGE,
   XLOG_BTREE_INSERT_META, XLOG_GIN_CREATE_PTREE and XLOG_GIN_DELETE_PAGE
   WAL records.   CLOG_TRUNCATE, XLOG_GIN_CREATE_PTREE, XLOG_HEAP_INIT_PAGE
   are not associated with bkp blocks Because they are handled in the same 
   module as other WAL record not associated with bkp, they will be
   safe enough.   On the other hand XLOG_BTREE_INSERT_META and 
   XLOG_GIN_DELETE_PAGE can be associated with bkp blocks.
   So far, I don't have good information how to generete them for the test.
   They will be tested once I have such information.
   So far, XLOG_BTREE_INSERT_META is handled in the same module as
   XLOG_BTREE_INSERT_LEAF and XLOG_BTREE_INSERT_UPPER.
   XLOG_GIN_DELETE_PAGE is handled by the same module as XLOG_BTREE_DELETE
   and many other WAL records.
