Re: citext operator precedence fix

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: citext operator precedence fix
Date: 2011-09-22 17:50:01
Message-ID: 4E7B7549.6010202@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2011-09-22 17:51:59 Re: citext operator precedence fix
Previous Message Kevin Grittner 2011-09-22 17:48:38 Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)