Re: common fe/be library (was Re: [PATCH] binary heap implementation)
Merlin Moncure <mmoncure@gmail.com>
From: Merlin Moncure <mmoncure@gmail.com>
To: Abhijit Menon-Sen <ams@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2013-01-14T15:16:31Z
Lists: pgsql-hackers
On Mon, Jan 14, 2013 at 4:55 AM, Abhijit Menon-Sen <ams@2ndquadrant.com> wrote: > At 2012-11-15 12:08:12 -0500, robertmhaas@gmail.com wrote: >> >> Still, maybe we could have a src/framework directory that uses the >> same trick to produce a libpgframework that frontend code can use, >> and a lib pgframework_srv that can be linked into the backend. >> That's might not actually be that much work; we'd just need to >> clone all the existing src/port logic. > > Does anyone have further comments about Robert's idea above? Or > alternative suggestions about how to structure a library of routines > that can be used in either the backend or in client code (like the > binary heap implementation)? A couple observations: *) Not sure about the name: something like "libcommon"? *) This is useful and potentially good for many things. For example, maybe type manipulation code could be pushed into the common library at some point. merlin
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix memory leaks in record_out() and record_send().
- 273986bf0d39 9.3.0 cited