psql dumps core when entering invalid backslash command

Lukas Ertl (l.ertl@univie.ac.at) reports a bug with a severity of 2

PostgreSQL v. 7.1.1., running on FreeBSD 4.3, standard installation via the ports collection.

When entering an invalid backslash command in psql (like "\m"), psql dumps core, psql gives error "Invalid command", but then dumps core.

Sample Code
httplog=# \m
Invalid command \m. Try \? for help.
Segmentation fault (core dumped)

Upgrade to 7.1.2 when it comes out or get the latest from the 7.1 branch
from CVS.

--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter

On Mon, 21 May 2001, Peter Eisentraut wrote:

Lukas Ertl (l.ertl@univie.ac.at) reports a bug with a severity of 2

Sample Code
httplog=# \m
Invalid command \m. Try \? for help.
Segmentation fault (core dumped)

Upgrade to 7.1.2 when it comes out or get the latest from the 7.1 branch
from CVS.

When is 7.1.2 planned to be released?

regards,
le

--
Lukas Ertl eMail: l.ertl@univie.ac.at
WWW-Redaktion Tel.: (+43 1) 4277-14073
Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140
der Universit�t Wien

pgsql-bugs@postgresql.org writes:

psql dumps core when entering invalid backslash command

Yup, known bug inadvertently introduced in 7.1.1, already fixed for 7.1.2.

(Hey Marc, where is 7.1.2 anyway?)

regards, tom lane

pgsql-bugs@postgresql.org writes:

psql dumps core when entering invalid backslash command

Yup, known bug inadvertently introduced in 7.1.1, already fixed for 7.1.2.

(Hey Marc, where is 7.1.2 anyway?)

We were waiting on some optimizer change, I thought. I don't remember
the specifics but I thought it had to do with UNION plans. Also, there
was some talk of waiting to get a port added (QNX?).

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Bruce Momjian <pgman@candle.pha.pa.us> writes:

(Hey Marc, where is 7.1.2 anyway?)

We were waiting on some optimizer change, I thought. I don't remember
the specifics but I thought it had to do with UNION plans.

No such issue pending that I know of.

regards, tom lane