Re: [PATCH 3/8] Add support for a generic wal reading facility dubbed XLogReader
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: pgsql-hackers@postgresql.org
Cc: Heikki Linnakangas <hlinnakangas@vmware.com>, Robert Haas <robertmhaas@gmail.com>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, Alvaro Herrera <alvherre@2ndquadrant.com>, Simon Riggs <simon@2ndquadrant.com>
Date: 2012-09-17T10:01:41Z
Lists: pgsql-hackers
On Monday, September 17, 2012 11:07:28 AM Andres Freund wrote: > On Monday, September 17, 2012 10:30:35 AM Heikki Linnakangas wrote: > > On 17.09.2012 11:12, Andres Freund wrote: > > > On Monday, September 17, 2012 09:40:17 AM Heikki Linnakangas wrote: > > > If you don't want the capability to forward/filter the data and read > > > partial data without regard for record constraints/buffering your patch > > > seems to be quite a good start. It misses xlogreader.h though... > > > > Ah sorry, patch with xlogreader.h attached. > > Will look at it in a second. It seems we would need one additional callback for both approaches like: ->error(severity, format, ...) For both to avoid having to draw in elog.c. Otherwise it looks sensible although it has a more minimal approach (which might or might not be a good thing). The one thing I definitely like is that nearly all of it is tried and true code... Greetings, Andres -- 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