| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, The Hermit Hacker <scrappy(at)hub(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] TODO list updated |
| Date: | 2000-01-13 18:29:11 |
| Message-ID: | 16238.947788151@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> echo is a builtin in ksh and derivatives, but I don't think it's safe
>> to assume it is a builtin everywhere...
> I believe it is safe. csh and sh have it built in. Does anyone know of
> a shell that does not have echo builtin? How do you tell? Not sure.
I looked at the man pages for plain old Bourne shell on the oldest
systems I have access to (SunOS 4.1.4 and HPUX 9). They all say that
echo is a builtin. So I guess it's probably safe enough. There may
be a few hoary old machines where
echo "ALTER USER ... $password ..." | backend
is a security risk, but it seems like it should be a very minimal
problem. (Especially since even a non-builtin echo should be a live
process for only a *really* short interval, even if the backend takes
longer to process the command.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-01-13 18:30:06 | Re: [HACKERS] Copy from/to asymmetry |
| Previous Message | Karl DeBisschop | 2000-01-13 17:42:16 | Re: [HACKERS] TODO list updated |