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-20 17:19:08
Message-ID: (view raw, whole thread or download thread mbox)
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):  

  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 dbmirror
    elog(NOTICE, cpKeyData)
    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, ...)
    elog(NOTICE, "%s", ...)

This applies to all cpKeyData and cpFieldData,
and probably cpFieldName(?).

Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2002-11-20 17:39:30
Subject: Re: Different result when using '=' and 'like' in unicode
Previous:From: Malcolm HuttyDate: 2002-11-20 15:49:09
Subject: RULE: ON DELETE doesn't stack deletes

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