Included patches should fix following problems in the muti-byte

enabled PostgreSQL 6.4.

o binary cursor does not work
o pg_dumpall produces incorrect create database statemnt

Tatsuo Ishii
t-ishii@sra.co.jp
This commit is contained in:
Bruce Momjian 1998-12-12 22:04:09 +00:00
parent 439ef85b0d
commit 5c431eb1f2
2 changed files with 3 additions and 6 deletions

View File

@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/access/common/printtup.c,v 1.36 1998/11/27 19:51:28 vadim Exp $
* $Header: /cvsroot/pgsql/src/backend/access/common/printtup.c,v 1.37 1998/12/12 22:04:09 momjian Exp $
*
*-------------------------------------------------------------------------
*/
@ -289,12 +289,9 @@ printtup_internal(HeapTuple tuple, TupleDesc typeinfo)
/* variable length, assume a varlena structure */
len = VARSIZE(attr) - VARHDRSZ;
#ifdef MULTIBYTE
pq_putncharlen(VARDATA(attr), len);
#else
pq_putint(len, VARHDRSZ);
pq_putnchar(VARDATA(attr), len);
#endif
#ifdef IPORTAL_DEBUG
{
char *d = VARDATA(attr);

View File

@ -59,7 +59,7 @@ do
if createdb -help|grep encoding >/dev/null
then
echo "create database with encoding='`pg_encoding $ENCODING`' $DATABASE;"
echo "create database $DATABASE with encoding='`pg_encoding $ENCODING`';"
else
echo "create database $DATABASE;"
fi