Re: PATCH: CITEXT 2.0 v3 - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: PATCH: CITEXT 2.0 v3
Date
Msg-id AB235355-40E7-4B4D-8238-BC48AB6F5C28@kineticode.com
Whole thread Raw
In response to Re: PATCH: CITEXT 2.0 v3  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PATCH: CITEXT 2.0 v3  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Jul 15, 2008, at 07:09, Tom Lane wrote:

> Yeah, probably.  I don't think the "make check" path will support it
> because it doesn't install contrib into the temp installation.
> (You'd also need to have put the extra entry in parallel_schedule
> not serial_schedule, but it's not gonna work anyway.)

Well now that was cool to see. I got some failures, of course, but
nothing stands out to me as an obvious bug. I attach the diffs file
(with the citext.sql failure removed) for your perusal. What would be
the best way for me to resolve those permission issues? Or do they
matter for sanity-checking citext?

Thanks,

David



Attachment

pgsql-hackers by date:

Previous
From: Abhijit Menon-Sen
Date:
Subject: Re: Fwd: Proposal - UUID data type
Next
From: Mark Mielke
Date:
Subject: Re: Fwd: Proposal - UUID data type