Skip site navigation (1) Skip section navigation (2)

AW: Performance (was: The New Slashdot Setup (includes MySqlserver))

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: AW: Performance (was: The New Slashdot Setup (includes MySqlserver))
Date: 2000-05-24 15:11:41
Message-ID: 219F68D65015D011A8E000006F8590C604AF7D9A@sdexcsrv1.f000.d0188.sd.spardat.at (view raw or flat)
Thread:
Lists: pgsql-hackers
> > > 3. automatic_rowid = no
> > > 
> > > The description simply says Automatic rowid. Does this apply to
> > > query result sets or to the underlying relation? If the latter,
> > > PostgreSQL has, of course, an OID for every tuple in the
> > > database.
> > > 
> > I'll have them fix that. MySQL calls them "_rowid" and 
> apparently tests
> > only for these.
> 
> Well, I don't see _rowid in the SQL spec either, so we are both
> non-standard here, though I believe our OID is SQL3.

Which is imho not what the test is for. I think they mean ctid,
which again I think we should have a rowid alias for (as in Informix,
Oracle).

Andreas

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2000-05-24 15:17:38
Subject: Re: interactive pgsql book
Previous:From: Zeugswetter Andreas SBDate: 2000-05-24 15:07:23
Subject: AW: More Performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group