Re: pg_basebackup failed to back up large file
| От | Tom Lane |
|---|---|
| Тема | Re: pg_basebackup failed to back up large file |
| Дата | |
| Msg-id | 20715.1401894850@sss.pgh.pa.us обсуждение |
| Ответ на | Re: pg_basebackup failed to back up large file (Magnus Hagander <magnus@hagander.net>) |
| Ответы |
Re: pg_basebackup failed to back up large file
|
| Список | pgsql-hackers |
Magnus Hagander <magnus@hagander.net> writes:
> On Tue, Jun 3, 2014 at 6:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Another thought is we could make pg_basebackup simply skip any files that
>> exceed RELSEG_SIZE, on the principle that you don't really need/want
>> enormous log files to get copied anyhow. We'd still need the pax
>> extension if the user had configured large RELSEG_SIZE, but having a
>> compatible tar could be documented as a requirement of doing that.
> I think going all the way to pax is the proper long-term thing to do, at
> least if we can confirm it works in the main tar implementations.
> For backpatchable that seems more reasonable. It doesn't work today, and we
> just need to document that it doesn't, with larger RELSEG_SIZE. And then
> fix it properly for the future.
Agreed, this would be a reasonable quick fix that we could replace in
9.5 or later.
regards, tom lane
В списке pgsql-hackers по дате отправления: