Re: Enabling frontend-only xlog "desc" routines
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-29T20:09:46Z
Lists: pgsql-hackers
On 2012-11-29 15:03:48 -0500, Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.com> writes: > > The other interesting question remaining is what to do about the rm_desc > > function in rmgr.c. We're split between these two ideas: > > Why try to link rmgr.c into frontend versions at all? Just make > a new table file that only includes the desc function pointers. > Yeah, then there would be two table files to maintain, but it's > not clear to me that it's uglier than these proposals ... Seems more likely to get out of sync. But then, rmgr.c isn't changing that heavily... I still prefer the -DFRONTEND solutions, but once more, its only a slight preference. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Move "hot" members of PGPROC into a separate PGXACT array.
- ed0b409d2234 9.2.0 cited