From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ALTER TYPE 0: Introduction; test cases |
Date: | 2011-01-16 22:20:52 |
Message-ID: | AANLkTi=WJ=U-GAtd1XTnMRktccPJXKGfDyxw0NEZrikR@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 16, 2011 at 12:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sat, Jan 15, 2011 at 10:25 AM, Noah Misch <noah(at)leadboat(dot)com> wrote:
>>> Do you value test coverage so little?
>
>> If you're asking whether I think real-world usability is more
>> important than test coverage, then yes.
>
> Quite honestly, I'd be inclined to rip out most of the DEBUG messages I
> see in that regression test altogether. They are useless, and so is the
> regression test itself. An appropriate regression test would involve
> something more like checking that the relfilenode changed and then
> checking that the contained data is still sane.
From my point of view, the value of those messages is that if someone
is altering or clustering a large table, they might like to get a
series of messages: rewriting the table, rebuilding this index,
rebuilding that index, rewriting the toast table index, .... as a
crude sort of progress indication.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2011-01-16 22:23:39 | Re: texteq/byteaeq: avoid detoast [REVIEW] |
Previous Message | Noah Misch | 2011-01-16 22:16:51 | Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql |