Re: Adding error message "source" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Adding error message "source"
Date
Msg-id 3342.1249568451@sss.pgh.pa.us
Whole thread Raw
In response to Re: Adding error message "source"  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Adding error message "source"  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Wed, Aug 5, 2009 at 16:11, Heikki
> Linnakangas<heikki.linnakangas@enterprisedb.com> wrote:
>> Would you like to propose a concrete list sources that we would have?
>> The implementation effort depends a lot on the categorization.

> Well, the only one I have a direct usecase for is the one that is "I
> want logs that are created because of typos in a psql client, or
> because an application does bad things (sends broken queries, bad
> escaping, NULL in not-NULL field etc) to not clutter up the log when I
> look for information about checkpoints and log archiving".

Well, it seems like you could get 90% of the way there just by filtering
on the PID --- watching the bgwriter, walwriter, and archiver should
cover this use-case reasonably well.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables
Next
From: Magnus Hagander
Date:
Subject: Re: Adding error message "source"