Re: [PROPOSAL] Inputs on forcing VACUUM VERBOSE to write timestamp

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: dinesh kumar <dineshkumar02(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PROPOSAL] Inputs on forcing VACUUM VERBOSE to write timestamp
Date: 2015-11-23 16:42:18
Message-ID: 565341EA.2080809@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/3/15 1:50 PM, Jeff Janes wrote:
> Unconvinced - sounds like you're just re-inventing log_line_prefix.
>
>
> Many times I've wanted a client_log_line_prefix. If someone wants to
> invent that, I'd second it.

It would be pretty awkward to have to turn that on and off to run a
manual vacuum, unless there was a LOGTIME option added to vacuum as well.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-11-23 16:50:17 Re: Truncating/vacuuming relations on full tablespaces
Previous Message Peter Eisentraut 2015-11-23 14:25:06 Re: documentation for wal_retrieve_retry_interval