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

Re: OID vs overall system performances on high load

From: PFC <lists(at)boutiquenumerique(dot)com>
To: "Andrew McMillan" <andrew(at)catalyst(dot)net(dot)nz>,"Eric Lauzon" <eric(dot)lauzon(at)abovesecurity(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: OID vs overall system performances on high load
Date: 2005-05-28 17:36:42
Message-ID: op.srhxvgdqth1vuj@localhost (view raw or flat)
Thread:
Lists: pgsql-performance

> The OID column is an extra few bytes on each row.  If you don't have any
> use for it (and let's face it: most of us don't), then create your
> tables "without OID".


	Also there are some useful hacks using the oid which don't work if it  
wraps around, thus preventing it from wrapping around by not using on  
every table could be useful in some cases...

In response to

pgsql-performance by date

Next:From: ellisDate: 2005-05-29 04:28:25
Subject: Re: Need help to decide Mysql vs Postgres
Previous:From: Andrew McMillanDate: 2005-05-28 05:08:10
Subject: Re: OID vs overall system performances on high load

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