From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: log_error_verbosity function display |
Date: | 2010-02-11 19:39:24 |
Message-ID: | 201002111939.o1BJdOx17585@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jaime Casanova wrote:
> On Thu, Feb 11, 2010 at 6:03 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > Of course, maybe the word LOCATION is wrong and it should be FUNCTION:
> >
> > ? ? ? ?ERROR: ?42P01: relation "lkjasdf" does not exist at character 15
> > ? ? ? ?FUNCTION: ?parserOpenTable(), parse_relation.c:858
> > ? ? ? ?STATEMENT: ?select * from lkjasdf;
> >
>
> i like this with or without the (), but maybe we are breaking client
> apps if change that
Ah, so you like FUNCTION. We usually modify log information to improve
clarity. We aren't as strict in changes to log/admin stuff as we are
with SQL stuff.
Also, the exact content of log_error_verbosity wasn't even documented
until 9.0 with a pending patch I have.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-02-11 19:40:51 | Re: log_error_verbosity function display |
Previous Message | Alvaro Herrera | 2010-02-11 19:38:53 | Re: [PATCH] Provide rowcount for utility SELECTs |