RE: AW: [HACKERS] Getting OID in psql of recent insert

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Zeugswetter Andreas SEV" <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: AW: [HACKERS] Getting OID in psql of recent insert
Date: 1999-11-23 09:44:51
Message-ID: 000b01bf3597$6340fb00$2801007e@cadzone.tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: owner-pgsql-hackers(at)postgreSQL(dot)org
> [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Zeugswetter
> Andreas SEV
> Sent: Tuesday, November 23, 1999 5:58 PM
> To: 'pgsql-hackers(at)postgreSQL(dot)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(at)tpf(dot)co(dot)jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SEV 1999-11-23 10:31:04 SQL statements: begin and end
Previous Message SAKAIDA Masaaki 1999-11-23 09:24:52 Re: [HACKERS] Getting OID in psql of recent insert