Re: A single escape required for log_filename

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, 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-02-06 18:08:01
Message-ID: 603c8f070902061008t215703fdqffc697b55da719fb@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 6, 2009 at 12:44 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Peter Eisentraut wrote:
>> On Wednesday 14 January 2009 05:23:53 Tom Lane wrote:
>> > However, since there's no standard strftime escape for epoch,
>> > Robert's proposal to rip out the functionality would break any existing
>> > code that still depends on this formatting option.
>>
>> 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.
>
> Are we doing anything about this for 8.4?

The patch is trivial and unlikely to break anything, but Tom wasn't
sure it made sense to change the behavior. I believe he's in the
minority, though.

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-02-06 18:19:32 Re: libpq WSACleanup is not needed
Previous Message Alvaro Herrera 2009-02-06 18:04:47 Re: new GUC var: autovacuum_process_all_tables