Re: citext operator precedence fix - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: citext operator precedence fix
Date
Msg-id 4E7B7549.6010202@agliodbs.com
Whole thread Raw
In response to Re: citext operator precedence fix  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: citext operator precedence fix
List pgsql-hackers
On 9/22/11 10:26 AM, David E. Wheeler wrote:
> On Sep 22, 2011, at 10:11 AM, Josh Berkus wrote:
> 
>>> That's what tests are for.
>>
>> So, tell me how to write a test to check which function is being used.
> 
> Just write some comparisons like upthread, and see if the output is f or t. Put them into sql/citext.sql.

Oh, ok.  I thought you meant checking the actual function call.

Tests go in the main SQL file?  Shouldn't they have their own file?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
Next
From: "David E. Wheeler"
Date:
Subject: Re: citext operator precedence fix