getopt_long patch for pg_dump and psql

Started by Kenji Sugitaabout 24 years ago4 messagespatches
Jump to latest
#1Kenji Sugita
sugita@sra.co.jp

Illegal long options to pg_dump makes core on some systems, since it lacks the
last null sentinel of struct option array.

Attached is a patch made by Mr. Ishida Akio <iakio@pjam.jpweb.net>.

Attachments:

getopt_long.patchtext/plain; charset=us-asciiDownload+3-1
#2Tatsuo Ishii
ishii@postgresql.org
In reply to: Kenji Sugita (#1)
Re: getopt_long patch for pg_dump and psql

Illegal long options to pg_dump makes core on some systems, since it lacks the
last null sentinel of struct option array.

Attached is a patch made by Mr. Ishida Akio <iakio@pjam.jpweb.net>.

Fix committed to 7.2-stable branch. (The patches did not apply to
current).
--
Tatsuo Ishii

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Tatsuo Ishii (#2)
Re: getopt_long patch for pg_dump and psql

Tatsuo Ishii <t-ishii@sra.co.jp> writes:

Fix committed to 7.2-stable branch. (The patches did not apply to
current).

I fixed the problem in current pg_dump when I saw Sugita's report,
since I was editing those files anyway. The problem may still exist
in current psql though.

regards, tom lane

#4Tatsuo Ishii
ishii@postgresql.org
In reply to: Tom Lane (#3)
Re: getopt_long patch for pg_dump and psql

Tatsuo Ishii <t-ishii@sra.co.jp> writes:

Fix committed to 7.2-stable branch. (The patches did not apply to
current).

I fixed the problem in current pg_dump when I saw Sugita's report,
since I was editing those files anyway. The problem may still exist
in current psql though.

Ok, fix for psql(startup.c) committed.
--
Tatsuo Ishii