Re: Proposed GUC Variable

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Proposed GUC Variable
Дата
Msg-id 200208272105.g7RL5Y318829@candle.pha.pa.us
обсуждение исходный текст
Ответ на Re: Proposed GUC Variable  (Larry Rosenman <ler@lerctr.org>)
Ответы Re: Proposed GUC Variable
Re: Proposed GUC Variable
Список pgsql-hackers
Larry Rosenman wrote:
> On Tue, 2002-08-27 at 15:54, Bruce Momjian wrote:
> > 
> > I had an idea on this.  It seems pretty pointless to show a query error
> > without a query, but some queries are very large.
> > 
> > How about if we print only the first 80 characters of the query, with
> > newlines, tabs, and spaces reduced to a single space, and send that as
> > LOG to the server logs.  That would give people enough context, and
> > prevent us from having another GUC variable.
> Not necessarily giving enough context.  I know I've had program
> generated query's that were syntactically invalid WAY after the 80th
> character. 
> 
> If you print ANY of the query, you should print all of it.  Look at the
> code in elog.c that does the syslog splitting.  

But we should have some default to print some of the query, because
right now we print none of it. I am not saying it is perfect, but it is
better than what we have, and is a reasonable default.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Rod Taylor
Дата:
Сообщение: Re: Proposed GUC Variable
Следующее
От: Oliver Elphick
Дата:
Сообщение: Re: Open 7.3 items