| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: The pgrminclude problem |
| Date: | 2012-08-20 16:03:06 |
| Message-ID: | 1345478202-sup-3389@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Hunsaker | 2012-08-20 16:03:11 | Re: Unexpected plperl difference between 8.4 and 9.1 |
| Previous Message | Tom Lane | 2012-08-20 15:58:07 | Re: Primary Key Constraint on inheritance table not getting route to child tables |