src/tools/pginclude considered harmful (was Re: [PATCHES] toast index entries again)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, Kris Jurka <books(at)ejurka(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>
Subject: src/tools/pginclude considered harmful (was Re: [PATCHES] toast index entries again)
Date: 2006-07-14 18:20:58
Message-ID: 3248.1152901258@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Kris Jurka <books(at)ejurka(dot)com> writes:
> The inclusion of access/tuptoaster.h in access/common/indextuple.c brought
> in the define of TOAST_INDEX_HACK which compresses large index entries.
> When this was removed the entries were no longer compressed which caused
> btree_gist to fail.

This is seriously scary, as it seems quite possible that there are other
similar cases in which we have simply silently lost functionality or
performance, and none of the regression tests will expose it.

In combination with the amount of time wasted over the past two days,
it is now perfectly clear that the existing pginclude tools are not
NEARLY good enough to detect what they are breaking. I would like to
propose that we revert all the include-related changes of the past two
days, and that src/tools/pginclude be removed from the CVS tree, until
such time as it is rewritten to be much smarter about what it is doing.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-07-14 18:43:35 Re: putting CHECK_FOR_INTERRUPTS in qsort_comparetup()
Previous Message Stefan Kaltenbrunner 2006-07-14 18:08:11 Re: contrib promotion?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-07-14 18:37:56 Re: Maintenance and External Projects (try 2)
Previous Message Kris Jurka 2006-07-14 18:08:08 toast index entries again