| From: | dinesh kumar <dineshkumar02(at)gmail(dot)com> | 
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> | 
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: [PROPOSAL] Inputs on forcing VACUUM VERBOSE to write timestamp | 
| Date: | 2015-09-03 16:53:24 | 
| Message-ID: | CALnrH7qqwbgUyM7o=HjCTENWFHP2vbyV7msoDM53PF=HM2tQKw@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Thu, Sep 3, 2015 at 9:48 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2015-09-03 21:45:52 +0530, dinesh kumar wrote:
> > Forcing VACUUM VERBOSE to write timestamp, for each "INFO" entry. This
> was
> > raised already in this
> > <
> http://www.postgresql.org/message-id/20031110162349.65542.qmail@web21408.mail.yahoo.com
> >
> > thread, and wanted to discuss it again. I didn't see any replies on this
> > old thread.
>
> Unconvinced - sounds like you're just re-inventing log_line_prefix.
>
> Thanks for your inputs.
I thought, it will be helpful without modifying the log_min_messages
parameter. Otherwise, we have to run the vacuum verbose, by modifying the
log_min_messages at session level, which will be recorded in pg_log.
If we allow VERBOSE to log timestamp, we can have it in stdout, which can
be diverted to a required log file. This will be useful for the vacuumdb
binary too.
Let me know your thoughts.
Regards,
Dinesh
manojadinesh.blogspot.com
> Greetings,
>
> Andres Freund
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shulgin, Oleksandr | 2015-09-03 16:57:31 | Re: Proposal: Implement failover on libpq connect level. | 
| Previous Message | Robert Haas | 2015-09-03 16:50:37 | Re: Performance improvement for joins where outer side is unique |