On 5/28/12 2:55 PM, Robert Haas wrote:
As far as CSV goes, I think the biggest deficiency is that there's a
mismatch between the way that log files are typically named (e.g. one
per day, or one per hour) and the way that a CSV foreign table is
created (you've got to point it at one particular fil
> The CSV format is both rich and
> machine-parseable (good start!) but it takes an unreasonable amount of
> work to make it usefully queryable. We need something that looks more
> like a big red button.
Hello,
The Pg logs consist of a rich soup with many different information kind.
It's comfor
On Mon, May 28, 2012 at 2:21 PM, Christopher Browne wrote:
>> Yeah, I agree. I think what is missing here is something that can be read
>> (and maybe indexed?) like a table, but written by a pretty dumb process.
>> It's not terribly workable to have PG log to PG, because there are too many
>>
On Mon, May 28, 2012 at 1:45 PM, Robert Haas wrote:
> On May 28, 2012, at 11:57 AM, Christopher Browne wrote:
>> 2. Ask Syslog
>>
>> My favorite way to configure *my* PG instances (e.g. - those that I
>> use for testing) is for them to forward messages to syslog. That way
>> they, and my Slony
On May 28, 2012, at 11:57 AM, Christopher Browne wrote:
> All interesting...
>
> We've got several models as to how logs are likely to be captured,
> which mean that it'll be difficult to have one uniform answer.
>
> 1. An easy traditional default is to capture logs in a log directory.
>
> An
On Mon, May 28, 2012 at 11:39 AM, Dimitri Fontaine
wrote:
> Stephen Frost 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, bas
Stephen Frost 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,
On Mon, May 21, 2012 at 05:53:55PM -0700, Josh Berkus wrote:
> Hackers,
>
> There's a lot of great information in the postgres logs. While we
> eventually want to get more sophisticated about providing users with
> status and history information, for 9.3 it would be really nice to
> just offer th
Josh,
* Josh Berkus (j...@agliodbs.com) wrote:
> Certainly this can be done ad-hoc using CSV format and csv_fdw.
> However, such setups are fragile due to log rotation and other issues.
> It seems like we could come up with a better way. Ideas?
This is really where I was hoping to eventually get
Hackers,
There's a lot of great information in the postgres logs. While we
eventually want to get more sophisticated about providing users with
status and history information, for 9.3 it would be really nice to just
offer the current logs in system view format.
Certainly this can be done ad-hoc
10 matches
Mail list logo
