[HACKERS] why table.name is translated to (name.*)::name?

2010-03-30 Thread Pavel Stehule
Hello, I was noticed on little bit strange feature of PostgreSQL 8.4 and 9.0 we can use a non existing column name. What does mean? postgres=# create table h(a int, b int); CREATE TABLE Time: 2,604 ms postgres=# insert into h values(199,22); INSERT 0 1 Time: 0,970 ms postgres=# explain verbose

Re: [HACKERS] why table.name is translated to (name.*)::name?

2010-03-30 Thread Ian Barwick
2010/3/30 Pavel Stehule pavel.steh...@gmail.com: Hello, I was noticed on little bit strange feature of PostgreSQL 8.4 and 9.0 we can use a non existing column name. What does mean? postgres=# create table h(a int, b int); CREATE TABLE Time: 2,604 ms postgres=# insert into h

Re: [HACKERS] why table.name is translated to (name.*)::name?

2010-03-30 Thread Tom Lane
Ian Barwick barw...@gmail.com writes: 2010/3/30 Pavel Stehule pavel.steh...@gmail.com: we can use a non existing column name. What does mean? FYI this has caused me (and presumably a few other people) a bit of head-scratching, e.g.:

Re: [HACKERS] why table.name is translated to (name.*)::name?

2010-03-30 Thread Pavel Stehule
2010/3/30 Tom Lane t...@sss.pgh.pa.us: Ian Barwick barw...@gmail.com writes: 2010/3/30 Pavel Stehule pavel.steh...@gmail.com: we can use a non existing column name. What does mean? FYI this has caused me (and presumably a few other people) a bit of head-scratching, e.g.: