| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding error message "source" |
| Date: | 2009-08-06 14:20:51 |
| Message-ID: | 3342.1249568451@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-08-06 14:23:11 | Re: Adding error message "source" |
| Previous Message | Kevin Grittner | 2009-08-06 13:51:08 | Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables |