This has been added to the TODO list.
> Problem Description:
> --------------------
> Using the SQL-command "COPY ... FROM" leads to the death of
> the backend when the oid-counter steps over the 2 billion
> frontier. As far as we could test, the other commands worked
> fine.
>
> --------------------------------------------------------------------------
>
> Test Case:
> ----------
> In our installation all 3 hours app. 4000000 datasets are
> cleared and reinstalled using the copy command. After the
> oids got bigger than 2147483647 the backend died during the
> copy command. After a fresh installation of Postgres (oids
> now starting again at 0) everything worked fine again.
>
> Not a fix, but maybe a hint:
> It seems to me that the internal representation of the oids
> is not consistent (long int - unsigned long int). I
> realized that the oid of ONE dataset sometimes was printed
> as a negative number and in other cases as a positive
> number (when big enough).
>
> --------------------------------------------------------------------------
>
> Solution:
> ---------
>
>
> --------------------------------------------------------------------------
>
>
>
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026