| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Automatic cleanup of oldest WAL segments with pg_receivexlog |
| Date: | 2017-02-26 21:48:01 |
| Message-ID: | CAB7nPqRiMjN94vnhT07mGgeNE7K39nqMFUSHYOYpbnf_n4U-ug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 24, 2017 at 11:58 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> Why not provide % replacements that contain that info? pg_receivexlog has a
> much better shot at doing that correctly than some random user tool...
>
> (%f could certainly be useful for other things)
(was unfortunately sent off-list, thanks Jim!)
%f maps with archive_command and restore_command, so for consistency
this makes sense, at least to me. And I cannot believe that all users
will actually need this argument, per se my use case upthread.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-02-26 21:49:03 | Re: [Bug fix] PQsendQuery occurs error when target_session_attrs is set to read-write |
| Previous Message | David Fetter | 2017-02-26 21:47:16 | Re: Statement timeout behavior in extended queries |