| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Cary O'Brien" <cobrien(at)Radix(dot)Net> |
| Cc: | mikeo(at)spectrumtelecorp(dot)com (mikeo), pgsql-general(at)hub(dot)org |
| Subject: | Re: Re: [SQL] oracle rownum equivalent? |
| Date: | 2000-06-08 14:38:14 |
| Message-ID: | 15872.960475094@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
"Cary O'Brien" <cobrien(at)Radix(dot)Net> writes:
> What I meant to say, and failed, was that in Oracle, rowid
> "psuedo-column" are hex encoded strings containing the block, row, and
> file where the tuple is stored. So lookup on unindexed rowid *should*
> be fast, although this is not spelled out in my ancient Oracle book.
Oh, in that case it's pretty much like our CTID column. For example:
regression=# select ctid,* from int8_tbl where ctid = '(0,3)';
ctid | q1 | q2
-------+------------------+-----
(0,3) | 4567890123456789 | 123
(1 row)
There is some code in 7.0 that tries to implement this in a fast way,
but I don't know how well it works...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Daniels | 2000-06-08 14:45:48 | Re: FreeBSD PostgreSQL7 port and v7.0.2 |
| Previous Message | Mirko Geffken | 2000-06-08 13:37:09 | Question reagarding serial type. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-08 14:39:26 | Re: ORDER BY in definition of views |
| Previous Message | Niall Smart | 2000-06-08 13:47:20 | ORDER BY in definition of views |