Re: Should we add crc32 in libpgport?

Daniel Farina <daniel@heroku.com> writes:
> Thinking unnecessary.  Motion is progress.  Here is a patch that uses
> this exact plan: pgport for the tables, broken out into a header file
> that is included in the building of libpgport.  I have confirmed by
> objdump -t that multiple copies of the table are not included in the
> postgres binary and the bloat has not occurred.

Applied with minor adjustments; mainly, I cleaned up some additional
traces of the old way of building pg_resetxlog and pg_controldata.

			regards, tom lane