dbmirror bug

Поиск
Список
Период
Сортировка
От Hai-Chen Tu
Тема dbmirror bug
Дата
Msg-id 20021122143130.6819.qmail@web9307.mail.yahoo.com
обсуждение исходный текст
Ответы Re: dbmirror bug  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: dbmirror bug  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Your name               : Hai-Chen Tu
Your email address      : hctu@yahoo.com


System Configuration
---------------------
  Architecture (example: Intel Pentium)         :

  Operating System (example: Linux 2.0.26 ELF)  :

  PostgreSQL version (example: PostgreSQL-7.3):
PostgreSQL-7.3

  Compiler used (example:  gcc 2.95.2)          :


Please enter a FULL description of your problem:
------------------------------------------------
dbmirror generates "out of memory" error in some
cases when the DEBUG_OUTPUT is enabled.




Please describe a way to repeat the problem.   Please
try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
The cause of the problem is that pending.c in dbmirror
uses
    elog(NOTICE, cpKeyData)
and
    elog(NOTICE, cpFieldData)
to print column data where elog
interprets the second argument as sprintf
format string, which fails if
cpKeyData/cpFieldData contains '%'.




If you know how this problem might be fixed, list the
solution below:
---------------------------------------------------------------------

The solution is to change
    elog(NOTICE, ...)
to
    elog(NOTICE, "%s", ...)

This applies to all cpKeyData and cpFieldData,
and probably cpFieldName.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus – Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

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

Предыдущее
От: Philip Warner
Дата:
Сообщение: Re: Is this planner choice easily explained?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Is this planner choice easily explained?