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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
