Re: [GENERAL] strange behavior, hoping for an explanation

2011-11-11 Thread Albe Laurenz
Chris Travers wrote: > I have found recently that tables in certain contexts seem to have a > name pseudocolumn. I was wondering if there is any documentation as > to what this is and what it signifies. > > postgres=# CREATE table TEST2 (a text, b text); > CREATE TABLE > postgres=# INSERT INTO te

Re: [GENERAL] strange behavior, hoping for an explanation

2011-11-10 Thread pasman pasmaƄski
See documentation, chapter Viii.E.2.2.2 2011/11/11, Chris Travers : > Hi; > > I have found recently that tables in certain contexts seem to have a > name pseudocolumn. I was wondering if there is any documentation as > to what this is and what it signifies. > > postgres=# CREATE table TEST2 (a te

Re: [GENERAL] strange behavior, hoping for an explanation

2011-11-10 Thread Tom Lane
Chris Travers writes: > I have found recently that tables in certain contexts seem to have a > name pseudocolumn. I was wondering if there is any documentation as > to what this is and what it signifies. I/O conversion cast from composite type to string. You might find this 9.1 patch informativ

[GENERAL] strange behavior, hoping for an explanation

2011-11-10 Thread Chris Travers
Hi; I have found recently that tables in certain contexts seem to have a name pseudocolumn. I was wondering if there is any documentation as to what this is and what it signifies. postgres=# CREATE table TEST2 (a text, b text); CREATE TABLE postgres=# INSERT INTO test2 values ('', ''); I