"Bryan White" <[EMAIL PROTECTED]> writes:
>> I'll take a look, but in the meantime you might be faced with an initdb
>> to bring the OID counter back under 2G :-(
> I tried creating the view on the main server and it worked just fine. If
> the OID limit has been exceeded, would not the database load fail miserably?
> Or are you saying that the limit is really 4G but there is a bug in 'create
> view' that limits it to 2G?
It should be 4G, but not all the code has been checked to make sure that
OIDs are always treated as unsigned rather than signed :-(. There are
probably more weak spots than just views ...
regards, tom lane
