Quoting Tom Lane <tgl@sss.pgh.pa.us>:
> Paul Caskey <paul@nmxs.com> writes:
> >> No doubt about it, you're likely to get a few "duplicate key" errors and
> >> stuff like that. I'm just observing that it's not likely to be a
> >> complete catastrophe, especially not if you don't rely on OIDs to be
> >> unique in your user tables.
>
> > I don't rely on OID uniqueness, but I assumed Postgres does!
>
> Only in the system tables, and not even in all of them. From the
> system's point of view, there's no real need to assign OIDs to
> user table rows at all --- so another possible answer is not to
> do that, unless the user requests it.
>
This changes things a lot. If the rows don't have to have OIDs associated with them
then the 4bn limit is not a transactional limit... in which case there shouldn't be a problem.
> regards, tom lane
>
Bradley Kieser
Director
Kieser.net
