Re: commit fests (was Re: primary key error message)

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: commit fests (was Re: primary key error message)
Date: 2010-01-23 15:28:12
Message-ID: 4B5B158C.60804@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bernd Helmle wrote:
>
>
> --On 22. Januar 2010 15:40:58 +0200 Peter Eisentraut <peter_e(at)gmx(dot)net>
> wrote:
>
>> Beta is still the definite cutoff; and the closer we get to
>> beta, the smaller the acceptable changes become. I think that formula
>> basically applies throughout the entire cycle.
>
> For someone like me it's hard to guess, what "small" means in that
> context. For example, i delayed my work on improving the
> representation of NOT NULL constraints in favor of the pg_table_size()
> patch (my time was too limited to work on both), since i always
> thought submitting beyond CF start would be a non-starter for such a
> thing.

It's a judgement call. I know that bothers the heck out of some people,
but hard and fast rules bug the heck out of others, so someone is going
to get bugged either way. As Ricky Nelson sang, "You can't please everyone."

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2010-01-23 15:47:54 Re: commit fests
Previous Message Bernd Helmle 2010-01-23 15:00:34 Re: commit fests (was Re: primary key error message)