Message-ID: <485952CF.2030600@pinpointresearch.com>
Date: Wed, 18 Jun 2008 11:24:15 -0700
From: Steve Crawford <scrawford@pinpointresearch.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080502)
MIME-Version: 1.0
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
CC: pgsql-admin@postgresql.org
Subject: Re: Major upgrade advice
References: <48594429.7040001@pinpointresearch.com>
	<200806182100.30833.achill@matrix.gatewaynet.com>
In-Reply-To: <200806182100.30833.achill@matrix.gatewaynet.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Achilleas Mantzios wrote:
> pg_dump by default ommits OIDs.
> However why do you want to completely remove OID functionality?
> space usage?
>   
It doesn't backup the OIDs themselves, but it does set "with oids" if 
the table had them. Per docs 
(http://www.postgresql.org/docs/8.3/static/runtime-config-compatible.html):

"The use of OIDs in user tables is considered deprecated, so most 
installations should leave this variable disabled. Applications that 
require OIDs for a particular table should specify WITH OIDS when 
creating the table. This variable can be enabled for compatibility with 
old applications that do not follow this behavior."

I want to incorporate current recommended practice with the upgrade. Per 
longstanding recommendation, we don't use OIDs. Saving 4-bytes/row on 
millions of rows is nice, too.

Cheers,
Steve