Skip site navigation (1) Skip section navigation (2)

Re: syslog performance when logging big statements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: syslog performance when logging big statements
Date: 2008-07-08 14:35:16
Message-ID: 8675.1215527716@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> writes:
> In this case, the INSERT *needs* 20 minutes to return. This is because the logging through syslog seems to severely slow the system.
> If instead, i use stderr, even with logging_collector=on, the same statement needs 15 seconds to return.

Hmm.  There's a function in elog.c that breaks log messages into chunks
for syslog.  I don't think anyone's ever looked hard at its performance
--- maybe there's an O(N^2) behavior?

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Achilleas MantziosDate: 2008-07-08 15:21:57
Subject: Re: syslog performance when logging big statements
Previous:From: Achilleas MantziosDate: 2008-07-08 12:24:46
Subject: syslog performance when logging big statements

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group