Re: Multi-byte and client side character encoding tests

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ayush Parashar <aparashar(at)greenplum(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Multi-byte and client side character encoding tests
Date: 2006-06-14 18:06:23
Message-ID: 4490501F.3030904@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:

>Tom Lane wrote:
>
>
>>Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>>
>>
>>>Where are we on this? Should we just add a URL to the full 1MB test files?
>>>
>>>
>>Adding an MB to the distribution for tests that hardly anyone needs to
>>run is surely not a good idea. What about putting them on pgfoundry and
>>then putting a link to that somewhere in the docs?
>>
>>
>
>Yea, that sounds good.
>
>
>

The running of extra tests outside our standard regression set will be
one of the topics discussed during my session in Toronto. I don't mind
having them stored elsewhere, although it will make things a bit more
complex, but this use should be kept in mind (for example, I don't think
pgfoundry has a CVSup server, although it probably could have easily
enough).

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2006-06-14 18:34:09 Re: postgresql and process titles
Previous Message Bruce Momjian 2006-06-14 17:56:12 Re: On hardcoded type aliases and typmod for user types