Re: PostgreSQL Developer meeting minutes up

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, Markus Wanner <markus(at)bluegap(dot)ch>, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Marko Kreen <markokr(at)gmail(dot)com>, Greg Stark <stark(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL Developer meeting minutes up
Date: 2009-06-06 20:05:30
Message-ID: 4A2ACC0A.1000006@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>> Any revision control system should be able to do better than diff/patch
>> as these systems have more information available to them. Normal GIT
>> uses the relatively common 3-way merge based upon the most recent common
>> ancestor algorithm. Assuming there is a most recent common ancestor that
>> isn't "file creation", it will have a better chance of doing the right
>> thing.
>>
>
> And I still haven't seen any actual evidence. Could we have fewer
> undocumented assertions and more experimental evidence? Take Andrew's
> plperl patches and see if git does any better with them than plain patch
> does. (If it's not successful with that patch, it's pointless to try it
> on any bigger cases, I fear.)
>
>
>

The plperl stuff is actually a tough case. In 7.4 we didn't have
provision for two interpreters, so PERL_SYS_INIT3 is called
unconditionally, and we didn't have a Windows port either, so the
comment is also different.

I guess that in itself illustrates the problems.

I also entirely agree with your point about us being more kludgey and
less invasive on back branches.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2009-06-06 20:08:47 Re: pg_migrator issue with contrib
Previous Message Tom Lane 2009-06-06 19:44:50 Partial vacuum versus pg_class.reltuples