From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How could we make it simple to access the log as a table? |
Date: | 2012-05-28 15:39:41 |
Message-ID: | m28vgciabm.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> This is really where I was hoping to eventually get to with the logging
> changes that have been discussed over the past couple of years. We need
> to have a mechanism to allow logging to different places, based on
> information included in the log message and/or context, where one of
> those places could potentially be some kind of receiver process that
> then dumps the message into a table, either on the local system or on a
> remote system.
That looks like syslog features?
> What exactly all of that looks like and how it works is a pretty big
> discussion, but I'd definitely love to hear from others who are
> interested in changes to our logging infrastructure.
I though about exposing the log CSV files as partitions of a log table,
each partition being a FDW able to read the file.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2012-05-28 15:57:32 | Re: How could we make it simple to access the log as a table? |
Previous Message | Tom Lane | 2012-05-28 15:16:24 | Re: Backends stalled in 'startup' state: index corruption |