Re: Large C files
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, Robert Haas <robertmhaas@gmail.com>, Peter Geoghegan <peter@2ndquadrant.com>, Peter Eisentraut <peter_e@gmx.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Jan Urbański <wulczer@wulczer.org>
Date: 2011-09-08T06:15:35Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix bug introduced by pgrminclude where the tablespace version name was
- f81fb4f69035 9.2.0 cited
On Wed, Sep 7, 2011 at 9:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Simon Riggs <simon@2ndQuadrant.com> writes: >> Please lets not waste effort on refactoring efforts in mid dev cycle. > > Say what? When else would you have us do it? When else would you have us develop? Major changes happen at start of a dev cycle, after some discussion. Not in the middle and especially not for low priority items. It's not even a bug, just code beautification. We've all accepted the need for some change, but I would like to see it happen slowly and carefully because of the very high risk of introducing bugs into stable code that doesn't have a formal verification mechanism currently. Anybody that could be trusted to make those changes ought to have something better to do. If they don't then that is in itself a much more serious issue than this. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services