Re: [PATCH 08/14] Store the number of subtransactions in xl_running_xacts separately from toplevel xids
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2012-11-15T12:07:23Z
Lists: pgsql-hackers
On 14 November 2012 22:17, Andres Freund <andres@2ndquadrant.com> wrote: > To avoid complicating logic we store both, the toplevel and the subxids, in > ->xip, first ->xcnt toplevel ones, and then ->subxcnt subxids. That looks good, not much change. Will apply in next few days. Please add me as committer and mark ready. > Also skip logging any subxids if the snapshot is suboverflowed, they aren't > useful in that case anyway. > This allows to make some operations cheaper and it allows faster startup for > the future logical decoding feature because that doesn't care about > subtransactions/suboverflow'edness. ...but please don't add extra touches of Andres magic along the way. Doing that will just slow down patch acceptance and its not important. I suggest to keep note of things like that and come back to them later. -- Simon Riggs 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 →
-
Background worker processes
- da07a1e85651 9.3.0 cited
-
Rearrange storage of data in xl_running_xacts.
- 5c11725867ac 9.3.0 cited
-
Basic binary heap implementation.
- 7a2fe9bd0371 9.3.0 cited
-
Embedded list interface
- a66ee69add6e 9.3.0 cited
-
Refactor xlog.c to create src/backend/postmaster/startup.c
- 9aceb6ab3c20 9.2.0 cited