Re: SQL MERGE patches for PostgreSQL Versions

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>, Kang Yuzhe <tiggreen87(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, bxzhai2010(at)gmail(dot)com
Subject: Re: SQL MERGE patches for PostgreSQL Versions
Date: 2017-06-22 12:51:14
Message-ID: 307c9800-082b-770b-0e20-b73f0c88b788@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/22/17 05:13, Craig Ringer wrote:
> On 22 June 2017 at 17:00, Kang Yuzhe <tiggreen87(at)gmail(dot)com> wrote:
>
>> diff --git a/src/backend/executor/nodeModifyTable.c
>> b/src/backend/executor/nodeModifyTable.c
>> index 8619ce3..e3ac758 100644
>> --- a/src/backend/executor/nodeModifyTable.c
>> +++ b/src/backend/executor/nodeModifyTable.c
>
> The first entry in the 'index' is the git commit hash of the base commit, IIRC.
I don't know what the technical term is, but these values are hashes of
the file before and after, or something like that. They are not Git
commits or trees.

See git format-patch option --base for how to communicate the base commit.

(The above patch was possibly created from an earlier unofficial Git
repository, because I can't find those hashes.)

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-06-22 13:13:56 Re: TRUE and true
Previous Message Alexander Korotkov 2017-06-22 12:35:13 Re: TRUE and true