From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Baldur Þór Emilsson <baldur(at)baldur(dot)biz> |
Cc: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Read data from WAL |
Date: | 2013-08-09 14:10:44 |
Message-ID: | 20130809141044.GO14729@alap2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2013-07-15 13:34:01 +0000, Baldur Þór Emilsson wrote:
> Thank you all for your responses. I'm aware of xlogdump but I'm afraid it
> does not help me with readign the data in the WAL. It is mainly "for
> debugging or educational purposes" (citing the docs) and it outputs a lot
> of information about the WAL records but not the contents of them (e.g. it
> says where an INSERT wrote the data, but not what the data is). Please
> correct me if I'm mistaken.
>
> What I'm looking for is a way to read the data that is inserted into the
> database. I was hoping there was some known way of doing that to save me
> the time it takes to patch Postgres to do that.
There's an in-development project doing that... Submitted to the last
commitfests and all. Search for changeset extraction et al.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | ascot.moss@gmail.com | 2013-08-09 14:17:50 | Re: Recovery.conf and PITR by recovery_target_time |
Previous Message | Pavel Stehule | 2013-08-09 14:04:29 | Re: plpgsql FOR LOOP CTE problem ? |