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

Re: [HACKERS] odd pg_dump output?

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: t-ishii(at)sra(dot)co(dot)jp
Cc: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] odd pg_dump output?
Date: 1998-08-29 16:27:14
Message-ID: 35E82BE2.D15EA577@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-hackers
> o fmtId() returns pointer to a static memory in it. In the meantime
> there is a line where is fmtId() called twice without saving the first
> value returned by fmtId(). So second call to fmtId() will break the
> first one.
> 
> o findTableByName() looks up a table by its name. if a table name
> contanins upper letters or non ascii chars, fmtId() will returns a
> name quoted in double quotes, which will not what findTableByName()
> wants. The result is SEG fault.

Thanks Tatsuo! But these are older problems, not new breakage from me,
right? Have you had a chance to test the latest pg_dump with your
patches? I'm still concerned that I didn't test pg_dump with a
regression test dump/reload/dump sequence (by comparing the two dump
files).

                       - Tom

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-08-29 17:22:05
Subject: Re: PostgreSQL under BSD/OS
Previous:From: Thomas G. LockhartDate: 1998-08-29 16:22:40
Subject: Re: [DOCS] Re: [HACKERS] vacuum problem

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