Andrew Sullivan <[EMAIL PROTECTED]> writes: > Ok, how then would one set the location of the config file?
The config file itself has to be found the same way we do it now, obviously: either a command line argument or the environment variable $PGDATA. But that's a red herring. This thread is not about where you find the config file, it's about locations for other files such as WAL logs and tablespaces. > And I presume this is all for the server only, right? Nobody is > talking about getting rid of (for instance) $PGPORT for clients, > right? I wasn't. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly