I said:
> While I now need to burrow into the IN-as-join code and find out where
> it's dropping the ball, I don't think this need stop you from making
> progress on the information schema. The reason the problem is appearing
> seems to be the implied cast that's getting introduced in the IN
> com
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The cited error message appears when loading the attached file (a cut-down
> version of a local development version of the information schema)
I've been able to reduce the problem to this test case:
drop view x1;
CREATE VIEW x1 AS
SELECT 1
F
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> On the last seven lines of the file I've marked a part that, when removed,
> makes the problem disappear, which might give a hint. Besides that, I'm
> clueless.
Looks like I must have broken this as a side-effect of IN-subselect
optimizations --- 7.3
The cited error message appears when loading the attached file (a cut-down
version of a local development version of the information schema) and then
running
select * from problem_schema.element_types;
On the last seven lines of the file I've marked a part that, when removed,
makes the problem di
