From: | Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: crazy logging from PG 8.4 |
Date: | 2013-10-23 18:56:30 |
Message-ID: | CAKuK5J3=boRoTDVvCXHQuriyu5w00mz8miTtUoNH1O7tp_eqYA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Oct 23, 2013 at 9:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Tomas Vondra" <tv(at)fuzzy(dot)cz> writes:
>> On 23 Říjen 2013, 16:00, Jon Nelson wrote:
>>> After several days of running a simple query over a very large dataset
>>> (more than a terabyte), I logged in to note that postgresql had
>>> decided to log *billions* of log lines.
>
>> First guess is that you enabled detailed logging in config.
>
> I think it's trace_sort.
I think you are right.
Let's say that there would end up being 2.7+ billion groups. Does
that scenario help to explain? I guess I'd like to see trace_sort have
a new value in addition to just "on" and "off", perhaps "external". I
don't really care about internal sorts but I do care about external
sorts. Right now, they're the only (minimal!) insight I have into how
the query is progressing.
--
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2013-10-23 19:48:27 | Re: crazy logging from PG 8.4 |
Previous Message | Tom Lane | 2013-10-23 14:54:49 | Re: crazy logging from PG 8.4 |