Re: Large C files
Jan Urbański <wulczer@wulczer.org>
From: Jan Urbański <wulczer@wulczer.org>
To: Peter Geoghegan <peter@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Peter Eisentraut <peter_e@gmx.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-09-06T23:22:29Z
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 07/09/11 01:13, Peter Geoghegan wrote: > On 6 September 2011 08:29, Peter Eisentraut <peter_e@gmx.net> wrote: >> I was thinking about splitting up plpython.c, but it's not even on that >> list. ;-) > > IIRC the obesity of that file is something that Jan Urbański intends > to fix, or is at least concerned about. Perhaps you should compare > notes. Yeah, plpython.c could easily be splitted into submodules for builtin functions, spi support, subtransactions support, traceback support etc. If there is consensus that this should be done, I'll see if I can find time to submit a giant-diff-no-behaviour-changes patch for the next CF. Cheers, Jan