From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)CommandPrompt(dot)com> |
Cc: | Devrim GÜNDÜZ <devrim(at)CommandPrompt(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Server does not start when log_statement_stats is set to on |
Date: | 2007-12-27 15:25:13 |
Message-ID: | 4703.1198769113@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)CommandPrompt(dot)com> writes:
> I think this makes plenty of sense. However, something that occured to
> me just now is that perhaps the right thing to do in the long term is to
> put this message in errcontext and leave the "invalid value for XXX" as
> the main error message. That would probably involve attaching a
> errcontext callback and removing the complaint_level from this message
> altogether, letting the outer caller deal with it.
errcontext wouldn't help --- by the time guc.c is ready to throw the
error, the assign hook isn't in the call stack anymore. We'd have to
invent some other special-purpose gizmo to make this work.
Might be worth doing, but again, seems too big a change for 8.3.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-12-27 16:55:47 | Re: Server does not start when log_statement_stats is set to on |
Previous Message | Tom Lane | 2007-12-27 15:17:08 | Re: BUG #3841: core dump in uuid-ossp |