From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_waldump command line arguments |
Date: | 2017-06-16 08:55:45 |
Message-ID: | CAFjFpRdvYQ_gXi3pyNdJzMO98=q_ys8uOz8n-4gD17ijBUA=wA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 16, 2017 at 2:38 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> A slightly broader concern is whether we need to require the start
> position at all. It seems like one could locate the WAL directory
> using the existing logic, then search for the earliest file. It might
> be a little unclear what "earliest" means when multiple timelines are
> present, but I bet we could come up with some behavior that would be
> convenient for most users.
We already have some default behaviour defined
--
-t timeline
--timeline=timeline
Timeline from which to read log records. The default is to use the
value in startseg, if that is specified; otherwise, the default is 1.
--
So, if startseg is not provided, choose the earliest file in the
default timeline (given by -t 1 when specified).
> It would be quite handy to be able to run
> this without arguments (or just with -z) and have it process all the
> WAL files that you've got on hand.
>
+1.
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2017-06-16 10:00:28 | Re: Restrictions of logical replication |
Previous Message | Masahiko Sawada | 2017-06-16 08:16:39 | Re: Get stuck when dropping a subscription during synchronizing table |