Re: Fwd: new patch of MERGE (merge_204) & a question about duplicated ctid
Greg Smith <greg@2ndquadrant.com>
From: Greg Smith <greg@2ndquadrant.com>
To: Erik Rijkers <er@xs4all.nl>
Cc: Boxuan Zhai <bxzhai2010@gmail.com>, pgsql-hackers@postgresql.org
Date: 2010-12-29T11:51:42Z
Lists: pgsql-hackers
Erik Rijkers wrote: > I get some whitespace-warnings, followed by error: > > $ git apply /home/rijkers/download/pgpatches/0091/merge/20101206/merge_204_2010DEC06.patch > /home/rijkers/download/pgpatches/0091/merge/20101206/merge_204_2010DEC06.patch:481: trailing > whitespace. > > /home/rijkers/download/pgpatches/0091/merge/20101206/merge_204_2010DEC06.patch:482: trailing > whitespace. > if (IsA(plan, ModifyTable) && > /home/rijkers/download/pgpatches/0091/merge/20101206/merge_204_2010DEC06.patch:550: trailing > whitespace. > /*print the action qual*/ > /home/rijkers/download/pgpatches/0091/merge/20101206/merge_204_2010DEC06.patch:556: trailing > whitespace. > (act_plan->operation == CMD_INSERT || > /home/rijkers/download/pgpatches/0091/merge/20101206/merge_204_2010DEC06.patch:560: trailing > whitespace. > > error: patch failed: src/backend/optimizer/plan/planner.c:739 > error: src/backend/optimizer/plan/planner.c: patch does not appl Maybe I'm doing something wrong, but I've never had good luck with git apply. I took this patch and applied it the 12/15 copy of HEAD I had checked out (trying to minimize drift in there since the patch was created) using: patch -p 1 < merge_204_2010DEC06.patch There was one trivial conflict it produced src/backend/optimizer/plan/planner.c.rej for, and that fix was straightforward to apply by hand. The result is now sitting as the merge204 branch in my github repo: https://github.com/greg2ndQuadrant/postgres/tree/merge204 if you did want to try this out. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us