| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: logfile subprocess and Fancy File Functions |
| Date: | 2004-07-23 21:22:49 |
| Message-ID: | 200407232122.i6NLMn604170@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane wrote:
> Also, while I'm aware that a superuser can persuade the backend to write
> on anything, it doesn't follow that we should invent pg_file_write(),
> pg_file_rename(), or pg_file_unlink(). Those are not needed for the
> originally intended purpose of this patch and I think that they are just
> invitations to trouble. If you are aware that there are burglars out
> there who know how to pick your door lock, do you then post directions
> and tools to help on your door?
We already allow COPY to write anywhere. Might as well give people some
utilities in case it is helpful.
I think the analogy is locking one door but leaving the other door
unlocked.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-07-23 21:23:41 | Re: Updated logging config (was: Initial eventlog support on win32 ) |
| Previous Message | Tom Lane | 2004-07-23 20:47:03 | Re: Updated logging config (was: Initial eventlog support on win32 ) |