Re: pg_upgrade
От | Bruce Momjian |
---|---|
Тема | Re: pg_upgrade |
Дата | |
Msg-id | 201009282000.o8SK0Pk02030@momjian.us обсуждение исходный текст |
Ответ на | Re: pg_upgrade (Brian Hirt <bhirt@me.com>) |
Ответы |
Re: pg_upgrade
Re: pg_upgrade |
Список | 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 clearlylarger 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.relnamespaceand 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@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-general по дате отправления: