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. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
