Re: pg_dump segfaults on command-line arguments?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Postgresql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump segfaults on command-line arguments?
Date: 2002-08-19 13:59:40
Message-ID: 6451.1029765580@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> This seems like such a silly thing I'm sure it's been fixed already.

Yeah, it has, but there's been no 7.2.2 release. You could get the
7.2-branch patch from the CVS archives:

2002-05-13 22:08 ishii

* src/bin/: pg_dump/pg_dump.c, psql/startup.c (REL7_2_STABLE): Fix
bug in pg_dump and psql (to reproduce the bug, just try pg_dump
--nonexistingoption).

per report from sugita(at)sra(dot)co(dot)jp on Thu, 09 May 2002 11:57:51 +0900
(JST) at pgsql-patches list.

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(at)pjam(dot)jpweb(dot)net>.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Eckermann 2002-08-19 14:14:33 Re: Success: Finished porting application to postgreSQL
Previous Message Tom Lane 2002-08-19 13:20:02 Re: Success: Finished porting application to postgreSQL