> You had that to begin with, and I changed it because I thought it was a
> bad idea. The directory name and file name should both make perfectly
> clear that the files are temp files belonging to Postgres. For example,
> it would be unsafe to make pg_tempfiles be a symlink pointing to a temp
> directory shared with other apps if there was any risk of temp file name
> collisions. (Not sure you'd do that anyway, because of security issues,
> but let's not foreclose it with a poor choice of file names.) A purely
> numeric file name for temp files is a particularly bad idea because it
> looks too much like our numeric names for table data files. Don't
> eliminate a hypothetical confusion factor between relnames and filenames
> (which are never seen in the same context anyway) by introducing one
> between filenames and other filenames.
>
> If you don't like pg_temp here, maybe post_temp? pgsql_temp?
What if I call the directory tmp or pgsql_tmp and the files
pgsql_pid_#.#?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026