| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dilip kumar <dilip(dot)kumar(at)huawei(dot)com> |
| Subject: | Re: pg_basebackup vs. Windows and tablespaces |
| Date: | 2014-11-13 21:49:56 |
| Message-ID: | CA+TgmoZ6+V=iLoyTsc5U8jPgOMv+2S51J9itsGzk9NMEfHdTZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 13, 2014 at 4:33 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> I'm not fully on board with that premise. (Get a better tar tool.
> Submit a patch.)
Noah was unable to find one that works:
http://www.postgresql.org/message-id/20130801161519.GA334956@tornado.leadboat.com
If most tar tools worked, and there was one that didn't, I think
that'd be a reasonable argument. But telling people to get a better
tool when they'd have to write it first seems rather unfriendly.
> But this also ties in with the recent discovery that the tar format
> cannot handle symlinks longer than 99 bytes. So this patch could also
> fix that problem by putting the untruncated name of the symlink in the
> WAL data.
Yeah, seems like a chance to kill two birds with one stone.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-11-13 21:50:21 | Re: REINDEX CONCURRENTLY 2.0 |
| Previous Message | Peter Eisentraut | 2014-11-13 21:33:08 | Re: pg_basebackup vs. Windows and tablespaces |