From: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Joshua Tolley <eggyknap(at)gmail(dot)com> |
Subject: | Re: WIP - syslogger infrastructure changes |
Date: | 2009-09-14 19:56:12 |
Message-ID: | 1d4e0c10909141256la2d0a2ew228b555c523b8fe5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Magnus,
On Mon, Sep 14, 2009 at 9:41 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> First, the patch removes the logging_collector parameter and basically
> assumes that logging_collector is always on.
Alvaro commited this a few days ago:
http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.225&r2=1.226
Any consequence?
> Second, data transfer from the backends is now in the form of
> structured data, and the actual logging message is put together in the
> syslogger (today,it's put together in the backend and just sent as a
> string to the syslogger). Yes, this means that we will likely send
> more data than what's eventually going to be logged, since all fields
> don't go out (except with CVS logging, I guess). But you usually don't
> send *that* much data in the log.
I don't know if it will make a real difference but some of us log
quite a lot of queries.
--
Guillaume
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-09-14 19:59:52 | Re: WIP - syslogger infrastructure changes |
Previous Message | Simon Riggs | 2009-09-14 19:41:44 | Re: Streaming Replication patch for CommitFest 2009-09 |