Re: Adding error message "source"

On Thu, Aug 6, 2009 at 16:20, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> On Wed, Aug 5, 2009 at 16:11, Heikki
>> Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)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.

Right. But that's pretty hard to do automated, since they will get a
new pid whenever the database is restarted. Which is hopefully not
very often, but still an issue. Plus, it's hard to do any kind of
historical look at things.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/