Re: The pgrminclude problem - Mailing list pgsql-hackers

From Robert Haas
Subject Re: The pgrminclude problem
Date
Msg-id CA+TgmoZm3dKHCWmvfDVwj6B6zkDYWRNSXUDR_7=+zrbTEvhMJQ@mail.gmail.com
Whole thread Raw
In response to Re: The pgrminclude problem  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Mon, Aug 20, 2012 at 12:03 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Excerpts from Robert Haas's message of lun ago 20 11:43:44 -0400 2012:
>> I actually think we'd probably be better off running pgrminclude once
>> per release cycle rather than any less often.  When the number of
>> changes gets into the hundreds or thousands of lines it becomes much
>> more difficult to validate that it's doing anything sensible.  I ran
>> it a while back and found a bunch of stuff that looked like it was
>> obviously worth fixing, but I was afraid of getting yelled at if I
>> went and fixed it, so I didn't.  Somehow that doesn't seem like an
>> ideal situation...
>
> Alternatively you could post a patch for comment.

Yeah, maybe I'll try that if I get back around to working on this at some point.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Large number of open(2) calls with bulk INSERT into empty table
Next
From: Andrew Dunstan
Date:
Subject: Re: sha1, sha2 functions into core?