Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.us> writes: > > Currently we output the ctid as a string: > > snprintf(buf, sizeof(buf), "(%u,%u)", blockNumber, offsetNumber); > > Perhaps someday we should consider outputting that as an array or a > > result set: > > It's not an array, because the two components are not of the same data > type; and it's not a result set, any more than (say) a point or a box > is. What it is is a record datatype. > > There might be some usefulness to adding SQL functions to allow > extraction of the block number and item number fields, though we'd have > some problems with the lack of a uint4 datatype to represent the block > number field's type. The demand for this has been too low to make me > feel we need to expend that effort...
Agreed, I was just pointing out that someday it might need improvement. -- Bruce Momjian http://candle.pha.pa.us SRA OSS, Inc. http://www.sraoss.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
