Re: [HACKERS] log_destination=file

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] log_destination=file
Date: 2018-03-02 23:06:09
Message-ID: CABUevExncdhEH0JOJsJyz2tw_neKc4cWPFAEa6n2ixEzwJrm2Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 2, 2018 at 7:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Mon, Jan 22, 2018 at 4:25 PM, Tomas Vondra
> > <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> >> Sorry for the naive question, but which of these bottlenecks are we
> >> actually hitting? I don't recall dealing with an actual production
> >> system where the log collector would be an issue, so I don't have a very
> >> good idea where the actual bottleneck is in this case.
>
> > Unfortunately, neither do I -- but I do believe that the problem is real.
>
> Not to state the obvious ... but if we do not know where the bottleneck
> is, isn't it a bit premature to be proposing changes to "fix" it?
>
> But that argument just leads to the same conclusion that seems to be
> prevalent at the moment, ie boot this to v12.
>

Just to be clear, it has already been booted to v12.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-03-02 23:08:00 Re: Documenting commitfest Rules
Previous Message Andres Freund 2018-03-02 22:40:56 Documenting commitfest Rules