| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | [PATCH] xlogreader-v4 |
| Date: | 2013-01-08 19:09:42 |
| Message-ID: | 1357672187-7693-1-git-send-email-andres@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: Andres Freund <andres(at)2ndquadrant(dot)com>
Subject: [PATCH] xlogreader-v4
In-Reply-To:
Hi,
this is the latest and obviously best version of xlogreader & xlogdump with
changes both from Heikki and me.
Changes:
* windows build support for pg_xlogdump
* xlogdump moved to contrib
* xlogdump option parsing enhancements
* generic cleanups
* a few more comments
* removal of some ugliness in XLogFindNextRecord
I think its mostly ready, for xlogdump minimally these two issues remain:
const char *
timestamptz_to_str(TimestampTz dt)
{
return "unimplemented-timestamp";
}
const char *
relpathbackend(RelFileNode rnode, BackendId backend, ForkNumber forknum)
{
return "unimplemented-relpathbackend";
}
aren't exactly the nicest wrapper functions. I think its ok to simply copy
relpathbackend from the backend, but timestamptz_to_str? Thats a heck of a lot
of code.
Patches 1 and 2 and 5 are just preparatory and probably can be applied
beforehand.
3 and 4 are the real meat of this and especially 3 needs some careful review.
Input welcome!
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-01-08 19:09:43 | [PATCH 1/5] Centralize Assert* macros into c.h so its common between backend/frontend |
| Previous Message | Josh Berkus | 2013-01-08 18:46:12 | Re: Cascading replication: should we detect/prevent cycles? |