From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: NOT boolfield kills backend |
Date: | 1998-09-22 19:20:44 |
Message-ID: | 199809221921.PAA26923@candle.pha.pa.us |
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...
I would guess something in the optimizer. Let me take a look at it.
Debugging patches, ah. No gdb yet?
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
http://www.op.net/~candle | (610) 353-9879(w)
+ If your life is a hard drive, | (610) 853-3000(h)
+ Christ can be your backup. |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-09-22 19:41:00 | Re: [HACKERS] current- crash |
Previous Message | Colin Dick | 1998-09-22 17:37:13 | Question re: null |