pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steve Crawford <scrawford@pinpointresearch.com>
To: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Major upgrade advice
Date: Wed, 18 Jun 2008 11:24:15 -0700
Message-ID: <485952CF.2030600@pinpointresearch.com> (raw)
In-Reply-To: <200806182100.30833.achill@matrix.gatewaynet.com>
References: <48594429.7040001@pinpointresearch.com>
	<200806182100.30833.achill@matrix.gatewaynet.com>

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




view thread (13+ messages)  latest in thread

Message-ID: <485952CF.2030600@pinpointresearch.com>
Permalink:  ../485952CF.2030600@pinpointresearch.com/
Also on:    postgresql.org/message-id/485952CF.2030600@pinpointresearch.com

 · 

reply

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-admin@postgresql.org
  Cc: scrawford@pinpointresearch.com, achill@matrix.gatewaynet.com
  Subject: Re: Major upgrade advice
  In-Reply-To: <485952CF.2030600@pinpointresearch.com>

* 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