| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "Prabakaran, Vaishnavi" <vaishnavip(at)fast(dot)au(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New option in pg_basebackup to exclude pg_log files during base backup |
| Date: | 2014-04-16 03:16:46 |
| Message-ID: | 534DF61E.8020708@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/9/14, 10:57 AM, Magnus Hagander wrote:
> So it'd be an array, and by default you'd have something like:
> basebackup_skip_path = $log_directory
> ?
>
> Maybe use it to skip backup labels by default as well.
> basebackup_skip_path = $log_directory, $backup_label_files
>
>
> I hadn't considered any details, but yes, someting along that line. And
> then you could also include arbitrary filenames or directories should
> you want.
What are the use cases for excluding anything else?
pg_basebackup ought to have some intelligence about what files are
appropriate to include or exclude, depending on what the user is trying
to do. It shouldn't become a general file copying tool.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sure.postgres | 2014-04-16 03:17:20 | The question about the type numeric |
| Previous Message | Tom Lane | 2014-04-16 03:11:05 | Re: [COMMITTERS] pgsql: Add TAP tests for client programs |