Re: [HACKERS] Parser/planner and column aliases

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Postgres Hackers List <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Parser/planner and column aliases
Date: 2000-02-03 17:00:54
Message-ID: 3899B446.FC71BE97@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I'm running across the behavior that an explicit select as above
> works, but if I try a wildcard expansion (select *...) instead of the
> explicit column listing the planner decides it needs to do some wild
> nested join stuff:

Hmm. Wildcarding like this works:

postgres=# select ty.* from t2 ty (b, c);
b | c
---+---
1 | 1
1 | 2
2 | 2
(3 rows)

So my problems are maybe just within the parser. Will keep looking at
it...

- Thomas

--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2000-02-03 17:04:15 Re: [HACKERS] Parser/planner and column aliases
Previous Message Tom Lane 2000-02-03 17:00:21 Re: [HACKERS] Another nasty cache problem