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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-08-29 17:22:05 | Re: PostgreSQL under BSD/OS |
Previous Message | Thomas G. Lockhart | 1998-08-29 16:22:40 | Re: [DOCS] Re: [HACKERS] vacuum problem |