Re: Additional logging for VACUUM and ANALYZE

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Additional logging for VACUUM and ANALYZE
Date: 2017-11-07 15:54:41
Message-ID: CAFcNs+pUSpoRO2FX7X+xb+D+zejWxT1iondBDDGXTt_5KLWyiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 7, 2017 at 1:35 PM, Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
>
> On 11/7/17, 9:13 AM, "Fabrízio Mello" <fabriziomello(at)gmail(dot)com> wrote:
> >> int save_nestlevel;
> >> + bool rel_lock;
> >>
> >
> > Just remove the additional tab indentation before rel_lock variable.
>
> I've removed the extra tab in v4.
>

Great. Changed status to ready for commiter.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2017-11-07 16:03:53 Re: Exclude pg_internal.init from base backup
Previous Message Bossart, Nathan 2017-11-07 15:35:03 Re: Additional logging for VACUUM and ANALYZE