From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | What's the meaning of system column in views |
Date: | 2002-05-14 00:34:59 |
Message-ID: | 3CE05BB3.9B83B464@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
I see the following for a view a_view;
# select ctid, xmin, cmin, xmax, cmax, tableoid from a_view;
ctid | xmin | cmin | xmax | cmax | tableoid
------+------+------+------+------+----------
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
(8 rows)
All system columns are null and seem to have no
meaning to me.
In addition it's also annoying to me e.g.
# create view aview as select ctid, * from a_table;
ERROR: name of column "ctid" conflicts with an existing system column
If there's no objection I would remove system columns
from views and allow the second example.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-14 00:37:35 | Re: pg_dump DROP commands and implicit search paths |
Previous Message | Neil Conway | 2002-05-14 00:33:58 | Re: pg_dump DROP commands and implicit search paths |