| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| 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-08 23:27:56 |
| Message-ID: | 20130808232756.GD6883@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 15, 2013 at 01:34:01PM +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 is no way to decode the WAL data as the decoding information is in
the database and not easily available to an external tool.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Konoplev | 2013-08-08 23:51:37 | Re: How to avoid Force Autovacuum |
| Previous Message | Adrian Klaver | 2013-08-08 23:18:37 | Re: Postgres won't start |