Re: pg_upgrade

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Brian Hirt <bhirt(at)me(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_upgrade
Date: 2010-09-28 20:00:25
Message-ID: 201009282000.o8SK0Pk02030@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Brian Hirt wrote:
> Looks like pg_upgrade is using 32bit oids. 2147483647 is the max signed 32 bit int, but the oids for my tables are clearly larger than that.
>
> == output from pg_upgrade ==
> Database: basement84_dev
> relname: mit.company: reloid: 2147483647 reltblspace:
> relname: mit.company_history: reloid: 2147483647 reltblspace:
>
> == output from catalog query ==
> basement84_dev=# select c.oid,c.relname from pg_catalog.pg_namespace n, pg_catalog.pg_class c where n.oid = c.relnamespace and n.nspname = 'mit';
> oid | relname
> ------------+--------------------
> 3000767630 | company
> 3000767633 | company_history
> (22 rows)
>

Interesting. Odd it would report the max 32-bit signed int. I wonder
if it somehow is getting set to -1. I looked briefly at the pg_upgrade
code and it appears to put all oids in unsigned ints.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Uckun 2010-09-28 20:14:46 Re: Killing "stuck" queries and preventing queries from getting "stuck"
Previous Message Chris Barnes 2010-09-28 19:48:00 Autovacuum settings between systems