contrib/ltree, contrib/tsearch, and contrib/tsearch2 each contain
implementations of CRC32 calculations.  I think these are now pretty
redundant with the CRC32 code existing in the main backend.  They
use a different CRC polynomial than the main backend code does,
but it's hard to credit that that is an important difference.
Anyone see a reason not to rip that code out and make these modules
use pg_crc.h/pg_crc.c instead?

			regards, tom lane

Responses

• Re: Drop separate CRC32 implementations in ltree, tsearch, at 2005-06-02 06:46:44 from Teodor Sigaev

pgsql-hackers by date

Next:	From: Oliver Jowett	Date: 2005-06-02 06:14:04
	Subject: Re: NOLOGGING option, or ?
Previous:	From: Alvaro Herrera	Date: 2005-06-02 05:17:26
	Subject: Re: NOLOGGING option, or ?