Re: merge command - GSoC progress - Mailing list pgsql-hackers

From Robert Haas
Subject Re: merge command - GSoC progress
Date
Msg-id AANLkTin4EXaz-x1+VYqZ3pm=o4YcTemRdzRMD-jpcH=G@mail.gmail.com
Whole thread Raw
In response to merge command - GSoC progress  (Boxuan Zhai <bxzhai2010@gmail.com>)
Responses Re: merge command - GSoC progress
List pgsql-hackers
On Tue, Jul 27, 2010 at 1:04 AM, Boxuan Zhai <bxzhai2010@gmail.com> wrote:
> I have get a edition that the merge command can run. It accept the standard
> merge command and can do UPDATE, INSERT and DELETE actions now. But we
> cannot put additional qualification for actions. There are some bugs when we
> try to evaluate the quals which make the system quit. I will fix it soon.

This patch doesn't compile.  You're using zbxprint() from a bunch of
places where it's not defined.  I get compile warnings for all of
those files and then a link failure at the end.  You might find it
useful to create src/Makefile.custom in your local tree and put
COPT=-Werror in there; it tends to prevent problems of this kind.

Undefined symbols: "_zbxprint", referenced from:     _transformStmt in analyze.o     _ExecInitMergeAction in
nodeModifyTable.o    _ExecModifyTable in nodeModifyTable.o     _ExecInitModifyTable in nodeModifyTable.o
_merge_action_plannerin planner.o
 

Not that it's as high-priority as getting this fully working, but you
should revert the useless changes in this patch - e.g. the one-line
change to heaptuple.c is obvious debugging leftovers, and all of the
changes to execQual.c and execUtil.c are whitespace-only.  You should
also try to make your code and comments conform to project style
guidelines.  In general, you'll find it easier to keep track of your
changes (and you'll have fewer spurious changes) if you use git diff
master...yourbranch instead of marking comments, etc. with ZBX or
similar.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Synchronous replication
Next
From: Josh Berkus
Date:
Subject: PostGIS vs. PGXS in 9.0beta3