| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Only first XLogRecData is visible to rm_desc with WAL_DEBUG |
| Date: | 2014-03-25 12:03:22 |
| Message-ID: | 20140325120322.GD9567@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
> On 03/25/2014 02:13 AM, Alvaro Herrera wrote:
> >You are not. I would rather have it fixed than removed, if possible. I
> >don't really care too much about getting a performance hit to palloc the
> >records, really; being able to actually read what's happening is much
> >more useful.
>
> I find it useful too, but I think pg_xlogdump can serve the same purpose.
>
> One thing missing from pg_xlogdump is the capability to keep
> tracking the inserted WAL, instead of dumping to the end of WAL and
> stopping there. If we add an option to pg_xlogdump to poll the WAL
> instead of bailing out at an error, I think it's a good replacement.
"tail -f"-style? If we can make that work I'm okay with removing it
from the backend.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2014-03-25 12:09:13 | Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation |
| Previous Message | Anastasia Lubennikova | 2014-03-25 09:14:50 | Re: GSoC proposal. Index-only scans for GIST |