Re: [HACKERS] odd pg_dump output? - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] odd pg_dump output?
Date
Msg-id 35E82BE2.D15EA577@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] odd pg_dump output?  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: [HACKERS] odd pg_dump output?  (t-ishii@sra.co.jp (Tatsuo Ishii))
Re: [HACKERS] odd pg_dump output?  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List 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

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [DOCS] Re: [HACKERS] vacuum problem
Next
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL under BSD/OS