Drop separate CRC32 implementations in ltree, tsearch, tsearch2? - Mailing list pgsql-hackers

From Tom Lane
Subject Drop separate CRC32 implementations in ltree, tsearch, tsearch2?
Date
Msg-id 10222.1117692017@sss.pgh.pa.us
Whole thread Raw
Responses Re: Drop separate CRC32 implementations in ltree, tsearch,
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: NOLOGGING option, or ?
Next
From: Oliver Jowett
Date:
Subject: Re: NOLOGGING option, or ?