| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
| Subject: | Re: A single escape required for log_filename |
| Date: | 2009-01-14 18:08:37 |
| Message-ID: | 603c8f070901141008x1a9f123fm993ac172364c68a1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> If it came down to this, then I'd say rip it out. Naming log files by epoch
> isn't exactly a user-friendly practice anyway, and there are equivalent but
> more readable formatting options available.
There are other alternatives but they're all ugly. For example, we
could make %0 (or some sequence that isn't taken) evaluate to the
empty string, or we could add another GUC to control the
interpretation of this GUC. But I don't think the ugliness is
justified in this instance.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2009-01-14 18:11:36 | Re: solaris libpq threaded build fails |
| Previous Message | Bruce Momjian | 2009-01-14 18:05:26 | Re: solaris libpq threaded build fails |