From: PFC <lists@boutiquenumerique.com>
To: Andrew McMillan <andrew@catalyst.net.nz>
To: Eric Lauzon <eric.lauzon@abovesecurity.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: OID vs overall system performances on high load
Date: Sat, 28 May 2005 19:36:42 +0200
Message-ID: <op.srhxvgdqth1vuj@localhost> (raw)
In-Reply-To: <1117256890.30150.179.camel@lamb.mcmillan.net.nz>
References: <F7B73864DD39FA40B6C56B3CE0D4D1CB634477@asdc003.abovesecurite.lan>
<1117256890.30150.179.camel@lamb.mcmillan.net.nz>
> 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...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lists@boutiquenumerique.com, andrew@catalyst.net.nz, eric.lauzon@abovesecurity.com
Subject: Re: OID vs overall system performances on high load
In-Reply-To: <op.srhxvgdqth1vuj@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox