Error messages crash backend

Some time in the last 48 hours, a problem was introduced that causes
any attempt at an error message to crash the backend:

| barsoom:tih> createdb
| barsoom:tih> psql
| Welcome to the POSTGRESQL interactive sql monitor:
| Please read the file COPYRIGHT for copyright terms of POSTGRESQL
|
| type \? for help on slash commands
| type \q to quit
| type \g or terminate with semicolon to execute query
| You are currently connected to the database: tih
|
| tih=> dfsasdfa;
| pqReadData() -- backend closed the channel unexpectedly.
| This probably means the backend terminated abnormally before
| or while processing the request.
| We have lost the connection to the backend, so further processing is
| impossible. Terminating.
| barsoom:tih>

I did 'gmake distclean', 'cvs update', 'configure', 'gmake all',
'gmake install', 'initdb', 'postmaster -i -S' and 'createuser tih'
just before what's logged above, so it was in a pristine environment.

Very strange. I have made some backend function parameter fixes, but
that should not change anything.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@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 <maillist@candle.pha.pa.us> writes:

Very strange. I have made some backend function parameter fixes, but
that should not change anything.

False alarm -- sorry. It turns out to be a bug in the signal handling
in NetBSD-current: when the backend tries to signal(myself,SIGQUIT), it
goes down in flames instead. I'll report it through channels.

-tih
--
Popularity is the hallmark of mediocrity. --Niles Crane, "Frasier"