| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Dilip kumar <dilip(dot)kumar(at)huawei(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, "Noah Misch" <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup vs. Windows and tablespaces |
| Date: | 2014-12-16 16:41:12 |
| Message-ID: | 549060A8.5060208@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/16/2014 06:30 PM, Andrew Dunstan wrote:
> I'm not clear why human readability is the major criterion here. As for
> that, it will be quite difficult for a human to distinguish a name with
> a space at the end from one without. I really think a simple encoding
> scheme would be much the best. For normal cases it will preserve
> readability completely, and for special cases it will preserve lack of
> any ambiguity.
Agreed. Besides, this:
16387 E:\\Program\ Files\\PostgreSQL\\tbs
is almost as human-readable as this:
16387 E:\Program Files\PostgreSQL\tbs
It's obvious how the escaping works, just by looking at the file.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-12-16 16:42:56 | Re: Commitfest problems |
| Previous Message | Jaime Casanova | 2014-12-16 16:39:53 | Re: Postgres TR for missing chunk |