From: Tom Lane <tgl@sss.pgh.pa.us>
To: Eric Lauzon <eric.lauzon@abovesecurity.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: OID vs overall system performances on high load
Date: Sun, 29 May 2005 17:47:18 -0400
Message-ID: <18634.1117403238@sss.pgh.pa.us> (raw)
In-Reply-To: <F7B73864DD39FA40B6C56B3CE0D4D1CB1B4466@asdc003.abovesecurite.lan>
References: <F7B73864DD39FA40B6C56B3CE0D4D1CB1B4466@asdc003.abovesecurite.lan>
"Eric Lauzon" <eric.lauzon@abovesecurity.com> writes:
> I am still in the dark due to my lack of knowledge on internal OID management,but
> i would presume that a table with OID enable and that has high load would require
> some more work from pgsql internal to maintain the OID index for the database.
There is no "OID index"; at least not unless you choose to create one
for a given table. The only thing particularly special about OID is
that there is an internal database-wide sequence generator for assigning
new values. Otherwise it works a whole lot like a serial column.
regards, tom lane
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: tgl@sss.pgh.pa.us, eric.lauzon@abovesecurity.com
Subject: Re: OID vs overall system performances on high load
In-Reply-To: <18634.1117403238@sss.pgh.pa.us>
* 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