Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Date
Msg-id CA+TgmoYNghdhojsjpvQMVke=R+m948-dBKKdoZAjTv+LPV8ZyQ@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Sun, Jul 17, 2011 at 8:44 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> My understanding of git notes is that they can be added after a commit
> without changing the commit - indeed that's apparently a large part of their
> raison d'être:
>
>   A typical use of notes is to supplement a commit message without
>   changing the commit itself. Notes can be shown by git log along with
>   the original commit message.

Right... but it's still append-only, and I think that there is little
reason to suppose that append-only is what we want or need here.

> It is a pity that you can't define extra fields as is suggested above.

Agreed.  The 'git way' is apparently to add things like:

Reviewed-by: So And So <so@so.com>

at the end of the commit message.

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Reduced power consumption in WAL Writer process
Next
From: Robert Haas
Date:
Subject: Re: Single pass vacuum - take 1