Skip site navigation (1) Skip section navigation (2)

Re: review of: collation for (expr)

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: probabble <probabble(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: review of: collation for (expr)
Date: 2012-03-02 01:30:19
Message-ID: CAJKUy5gmLwFqGSPp=RRppde0rWZSnDqOpm-9bUFTWP6_2KnStw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Jan 19, 2012 at 1:50 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On tor, 2012-01-12 at 21:25 -0800, probabble wrote:
>> Compiling on Ubuntu 10.04 LTS AMD64 on a GoGrid virtual machine from
>> 2012-01-12 checkout.
>>
>> Bison upgraded to v2.5, and downgraded to v2.4.1
>>
>> Make process for both versions resulted in the following errors:
>>
>> make[3]: Leaving directory `/usr/local/src/pgbuild/src/backend/catalog'
>> make -C parser gram.h
>> make[3]: Entering directory `/usr/local/src/pgbuild/src/backend/parser'
>> /usr/local/bin/bison -d  -o gram.c gram.y
>> gram.y: conflicts: 370 reduce/reduce
>> gram.y: expected 0 reduce/reduce conflicts
>> gram.y:10482.27-10494.33: warning: rule useless in parser due to conflicts:
>> func_expr: COLLATION FOR '(' a_expr ')'
>> make[3]: *** [gram.c] Error 1
>
> I can't reproduce that.
>

me neither

> In the meantime, attached is a re-merged version of the patch; the old
> version doesn't apply cleanly anymore.
>

besides a clash in the oid and the value of leakproof missing in the
pg_proc entry, everything works fine.

The only thing is that i don't see a reason for these includes in
src/backend/utils/adt/misc.c:

+ #include "nodes/nodeFuncs.h"
+ #include "utils/lsyscache.h"


-- 
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-03-02 01:32:23
Subject: Re: 16-bit page checksums for 9.2
Previous:From: Alvaro HerreraDate: 2012-03-02 00:45:36
Subject: Re: 16-bit page checksums for 9.2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group