Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run
Date
Msg-id 13484.1155658925@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run  (Andreas Pflug <pgadmin@pse-consulting.de>)
Responses Re: [PATCHES] [Patch] - Fix for bug #2558, InitDB failed to run
List pgsql-hackers
Andreas Pflug <pgadmin@pse-consulting.de> writes:
> what issues might arise if the output is redirected to a legal tmp file?

Well, (1) finding a place to put the temp file, ie a writable directory;
(2) ensuring the file is removed afterwards; (3) not exposing the user
to security hazards due to unsafe use of a temp file (ye olde
overwrite-a-symlink risk).  Perhaps a few more I didn't think of.

It's not a trivial change, and the evidence presented so far hasn't
convinced me that we need to put in the effort.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [PATCHES] Custom variable class segmentation fault
Next
From: Peter Eisentraut
Date:
Subject: Re: An Idea for planner hints