Skip site navigation (1) Skip section navigation (2)

Drop separate CRC32 implementations in ltree, tsearch, tsearch2?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Drop separate CRC32 implementations in ltree, tsearch, tsearch2?
Date: 2005-06-02 06:00:17
Message-ID: 10222.1117692017@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: 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

Responses

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group