Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jim Nasby <jim(at)nasby(dot)net>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Date: 2011-07-18 00:36:49
Message-ID: CA+Tgmob8BPTJy_C2CNYpTaUCJZE3t2EYyC-uKsT_JOVKDEY2nw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Sun, Jul 17, 2011 at 1:20 PM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> On Jul 12, 2011, at 11:30 AM, Joshua D. Drake wrote:
>>>> This all becomes much easier if we keep the ads out of the commit
>>>> messages, and stick to the technical side there. And find another
>>>> venue for the other credit.
>>>
>>> I'm open to ideas.
>>
>> I think the commit log isn't actually useful for the "advertising" portion of this. Users don't read commit logs for the most part. However, it is an easy way for people who are writing release notes, press releases, etc... to find the information.
>>
>> Is it a good place for the information? No.
>>
>> Is it the easiest place to store it until somebody steps up and creates a proper way to track it so that it can be desimnated properly throughout the community? Probably.
>>
>> We do need a way to track this information.
> +1 on everything Josh said.
>
> Does git allow for additional commit fields? That would allow for easy tracking without much additional burden on committers.

I mean, there's git notes, but that's not exactly what we're looking
for here, and I don't see how it would easy the burden on committers
anyway, and it doesn't solve the problem of not being able to change
things after the fact.  I think this is a clear-cut case of needing
some sort of web application to manage this.  I'd even be willing to
help fill in the relevant info.  But I'm not going to write it
myself...

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

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2011-07-18 00:44:53
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Previous:From: Peter GeogheganDate: 2011-07-18 00:20:16
Subject: Re: Reduced power consumption in WAL Writer process

pgsql-committers by date

Next:From: Andrew DunstanDate: 2011-07-18 00:44:53
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Previous:From: Bruce MomjianDate: 2011-07-17 22:39:19
Subject: Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group