Re: documentation for committing with git

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Daniel Farina <drfarina(at)acm(dot)org>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: documentation for committing with git
Date: 2010-08-05 03:03:59
Message-ID: 4C5A2A1F.2090804@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/04/2010 10:08 PM, Daniel Farina wrote:
> On Wed, Aug 4, 2010 at 6:29 AM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> All those issues can be avoided if you only run "git gc" when all the
>> working directories are in a clean state, with no staged but uncommitted
>> changes or other funny things. I can live with that gun tied to my ankle
>> ;-).
> Does even that open a possibility for data loss?
>
> Use of the alternates feature will, to my knowledge, never write the
> referenced repository: all new objects are held in the referencers.
> The only condition as I understand it is not to generate garbage in
> the reference repository, and that nominally does not happen in a repo
> that exists only to be an object pool (you probably even want to use a
> "bare" repository instead of one with checked out files).
>
>

AIUI, git-new-workdir, which Heikki is proposing to use, does not work
with bare clones.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-08-05 03:29:31 Re: BUG #5599: Vacuum fails due to index corruption issues
Previous Message Tom Lane 2010-08-05 02:37:25 Re: Re: [HACKERS] Drop one-argument string_agg? (was Re: string_agg delimiter having no effect with order by)