Skip site navigation (1) Skip section navigation (2)

dbmirror bug

From: Hai-Chen Tu <hctu(at)yahoo(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Cc: hctu(at)yahoo(dot)com
Subject: dbmirror bug
Date: 2002-11-22 14:31:30
Message-ID: 20021122143130.6819.qmail@web9307.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Your name               : Hai-Chen Tu    
Your email address      : hctu(at)yahoo(dot)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

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2002-11-22 15:38:39
Subject: Re: Is this planner choice easily explained?
Previous:From: Philip WarnerDate: 2002-11-22 14:13:03
Subject: Re: Is this planner choice easily explained?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group