Search Postgresql Archives

Re: pg_upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux