| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | "Kardos, Dr(dot) Andreas" <kardos(at)repas-aeg(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: [BUGS] pg_dumpall |
| Date: | 2000-03-09 00:38:48 |
| Message-ID: | Pine.LNX.4.21.0003081352440.387-100000@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kardos, Dr. Andreas writes:
> 2. FOO="`echo "$BAR"`"
>
> This construct I have found working on QNX4, Digital Unix, SunOS and Linux.
> But the problem seems not to be so simple. After removing the backslashes
> from the old pg_dumpall it didn't work any more on Digital Unix! So the
> escaped double quotes make sense somewhere in some context.
I'm inclined to say that it should work but probably doesn't everywhere.
But I need to fix this because all the scripts currently contain ``
sequences that need to be double-quoted because otherwise they will fail
if the installation path contains whitespace. (See those ${PATHNAME}
things.)
For now I might have to resort to yanking that PATHNAME logic again and
use the new pg_dumpall since it appears to magically work.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Elphick | 2000-04-01 14:02:44 | Bug#61519: Copy does not work with special characters? (fwd) |
| Previous Message | Peter Eisentraut | 2000-03-09 00:38:20 | Re: [BUGS] grant/revoke bug with delete/update |