Re: [BUG] False indication in pg_stat_replication.sync_state
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: masao.fujii@gmail.com
Cc: pgsql-hackers@postgresql.org
Date: 2012-10-19T07:37:29Z
Lists: pgsql-hackers
Attachments
- 20121019_sync_state_patch_v2.patch (text/x-patch) patch v2
Thank you for comment. > > I think this patch should be applied for 9.2.2 and 9.1.7. > > Looks good to me, though I don't think the source code comment needs > to be updated in the way the patch does. Ok, the patch for walsender.c becomes 1 liner, quite simple. However, I've forgotten to treat other three portions in walsender.c and syncrep.c also does XLogRecPtrIsInvalid(<XLogPtr which comes from WAL receiver>). This new patch includes the changes for them. By the way, XLogRecPtrIsInvliad() seems to be used also in gist.c, gistget.c, gistvacuum.c, visibilitymap.c, clog.c, slru.c, xlog.c. In these files, LSN's fed to XLogRecPtrIsInvalid() looks to be *valid* start point of WAL records, but I'm not sure of that. regards, -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Replace XLogRecPtr struct with a 64-bit integer.
- 0ab9d1c4b316 9.3.0 cited