RE: AW: [HACKERS] Getting OID in psql of recent insert - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: AW: [HACKERS] Getting OID in psql of recent insert
Date
Msg-id 000b01bf3597$6340fb00$2801007e@cadzone.tpf.co.jp
Whole thread Raw
In response to AW: AW: [HACKERS] Getting OID in psql of recent insert  (Zeugswetter Andreas SEV <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
> -----Original Message-----
> From: owner-pgsql-hackers@postgreSQL.org
> [mailto:owner-pgsql-hackers@postgreSQL.org]On Behalf Of Zeugswetter
> Andreas SEV
> Sent: Tuesday, November 23, 1999 5:58 PM
> To: 'pgsql-hackers@postgreSQL.org'
> Subject: AW: AW: [HACKERS] Getting OID in psql of recent insert 
> 
> > 
> > > Is someone still working on the xid access ?
> > 
> > I think we have the ability to refer to CTID in WHERE now, 
> 
> Do we use the sql syntax 'where rowid = :xxx' for it, 
> or do we say 'where ctid = :xxx'.
> I would like the rowid naming, because Informix, Oracle (and DB/2 
> ?) use it.
>

You could say 'where ctid= ...' in current tree.
It has been rejected due to the lack of equal operator for type TID. 
The syntax itself has been allowed by parser.
> > but not yet an access method that actually makes it fast...
> 
> Well that is of course only half the fun :-(
> Could it be done like an index access, 
> where the first part of the work is skipped, or tunneled through ?

I would commit the implementation of direct scan by tuple id soon.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] Concurrent VACUUM: first results
Next
From: Zeugswetter Andreas SEV
Date:
Subject: SQL statements: begin and end