| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>, "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RC1? |
| Date: | 2002-11-13 16:28:02 |
| Message-ID: | 22802.1037204882@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
>> Why use awk for this at all ? and not:
>> echo "\\set ECHO all"
Actually, some googling revealed the following advice (in the Autoconf
manual):
Because of these problems, do not pass a string containing
arbitrary characters to echo. For example, echo "$foo" is safe if
you know that foo's value cannot contain backslashes and cannot
start with -, but otherwise you should use a here-document like
this:
cat <<EOF
$foo
EOF
This seems obviously safer, so I shall make it do that instead
of relying on either awk or echo.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2002-11-13 16:38:13 | Re: RC1? |
| Previous Message | Tom Lane | 2002-11-13 16:00:55 | Re: Propose RC1 for Friday ... |