Re: NOT boolfield kills backend

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: NOT boolfield kills backend
Date: 1998-09-22 03:55:48
Message-ID: 36071FC4.8B283DE4@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hey Bruce! I've got some questions for the original topic, which was the
failure of

select not b from t;

where b is a boolean type in table t.

It looks to me that the NOT_EXPR expression node is being constructed
correctly in the parser, but somewhere between the parser and the
executor (at ExecSeqScan()) it is being transformed into a deficient
OP_EXPR expression node. Any hints on other places where this query tree
might be getting transformed or manipulated? If I brute force substitute
the expression type to be NOT_EXPR in ExecEvalExpr() then the query
completes successfully:

postgres=> select not b from t1;
?column?
--------
f
t
(2 rows)

Hints are appreciated, or if this is touching on areas you are already
familiar with I can send my debugging patches...

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-09-22 04:47:21 Re: [sferac@bo.nettuno.it: Re: [HACKERS] BUG: NOT boolfield kills backend]
Previous Message Marcus Mascari 1998-09-22 02:38:35 backend crashes under 6.4beta