From: | "Ayush Parashar" <aparashar(at)greenplum(dot)com> |
---|---|
To: | "Luke Lonergan" <llonergan(at)greenplum(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | "majordomo(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: multibyte regression tests |
Date: | 2005-07-15 21:32:09 |
Message-ID: | BEFD7969.724%aparashar@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew, Luke,
As pointed by Luke, the reason for using mb regression suite (src/test/mb),
is to consolidate all similar kinds of multi-byte/client encoding tests at
one place.
Thanks,
Ayush
On 7/15/05 1:36 PM, "Luke Lonergan" <llonergan(at)greenplum(dot)com> wrote:
>
> Andrew,
>
>> Good. So should we roll this up into the standard regression suite? Why
>> are these tests separate? Is it just that they need a UTF8 encoded db
>> rather than an SQL-ASCII encoded db?
>
> I think that was the idea - the src/test/mb kit was already there and was
> designed to create the UTF8 database and controlled circumstances for a
> conversion test, so we used it for the similar testing for COPY.
>
> It could possibly be moved into the "make check" regression suite, if the
> regression DB is always created with UTF8.
>
> Ayush may be able to add to this.
>
> - Luke
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2005-07-15 21:47:09 | Autovacuum name |
Previous Message | Andrew Dunstan | 2005-07-15 21:07:31 | Re: multibyte regression tests |