Re: WALInsertLock tuning
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Simon Riggs <simon@2ndquadrant.com>, Jeff Janes <jeff.janes@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-10-14T12:34:44Z
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 →
-
Introduce compact WAL record for the common case of commit (non-DDL).
- 465883b0a2b4 9.2.0 cited
On Thu, Oct 13, 2011 at 9:35 PM, Bruce Momjian <bruce@momjian.us> wrote: > > I assume this was addressed with this commit: > > commit 465883b0a2b4236ba6b31b648a9eabef3b7cdddb > Author: Simon Riggs <simon@2ndQuadrant.com> > Date: Tue Jun 28 22:58:17 2011 +0100 > > Introduce compact WAL record for the common case of commit (non-DDL). > XLOG_XACT_COMMIT_COMPACT leaves out invalidation messages and relfilenodes, > saving considerable space for the vast majority of transaction commits. > XLOG_XACT_COMMIT keeps same definition as XLOG_PAGE_MAGIC 0xD067 and earlier. > > Leonardo Francalanci and Simon Riggs No, that's completely unrelated. I think it just never quite made it to prime time - it was analyzed theoretically but some of the testing discussed on the thread doesn't seem to have been done. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company