| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Markus Bertheau <twanger(at)bluetwanger(dot)de> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposed GUC Variable |
| Date: | 2002-08-23 17:56:44 |
| Message-ID: | 87fzx58nmr.fsf@mailbox.samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Markus Bertheau <twanger(at)bluetwanger(dot)de> writes:
> On Fri, 2002-08-23 at 04:46, Bruce Momjian wrote:
> >
> > * Add GUC parameter to print queries that generate errors
>
> Maybe don't make that an option, but rather do it always. I don't
> see where that would hurt.
It would hurt in situations in which an error is expected to occur
(e.g. INSERT into table, if constraint violation then do XYZ). It
would also make the logs a lot larger + less readable if long (say,
100 line) queries are being executed.
I don't think either situation is particularly common, but I do think
it's worth keeping a GUC variable for it. The GUC var should probably
default to being enabled though.
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2002-08-23 18:16:02 | Re: v7.2.2 Released ... but not announced ... |
| Previous Message | Bruce Momjian | 2002-08-23 17:46:03 | Re: [GENERAL] integer[] Update Questions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2002-08-23 19:55:47 | Re: prepare patch |
| Previous Message | Bruce Momjian | 2002-08-23 15:24:19 | Re: Proposed GUC Variable |