Re: 4 billion + oids
От | Neil Conway |
---|---|
Тема | Re: 4 billion + oids |
Дата | |
Msg-id | 1048475647.6231.427.camel@tokyo обсуждение исходный текст |
Ответ на | 4 billion + oids ("Andrew Bartley" <abartley@evolvosystems.com>) |
Список | pgsql-general |
On Sun, 2003-03-23 at 21:35, Andrew Bartley wrote: > 1. Change all creation of temp tables with "without oids", hoping > to reduce the consumption of OIDS That should be the first thing you should do (in 7.4, there will be an ALTER TABLE command to disable OIDs). If you're not making use of OIDs in your application, you can specify WITHOUT OIDS for all user tables. IMHO this should be the default for CREATE TABLE some time in the near future. > 1. Check for the error string "Cannot insert a duplicate key into > unique index pg_class_oid_index" in the batch shells for each > function call and re-run if required. If you define all your tables (especially temp tables) using WITHOUT OIDS, you shouldn't need to bother with this. > Can anyone comment if they know this is a fundamental limitation of > PostgreSQL It's not a "fundamental limitation" at all, merely a problem of remaining backward compatible with the behavior of previous PostgreSQL releases. > We are running PostgreSQL 7.2.1 on Pentium 4 x86 type systems. Upgrading to the latest stable 7.2 release (7.2.4), or if possible 7.3.2, is always encouraged. Cheers, Neil
В списке pgsql-general по дате отправления: