The OIDs won't hurt except take a little disk space. The only thing is that
if they overflow you run a very small chance one of your DDL statements amy
fail.
This feature has only just become optional and everything worked fine before then.
Hope this helps,
On Fri, Jan 09, 2004 at 04:52:04PM -0800, Amir Khawaja wrote:
> Hi Everyone,
>
> I have a rather trivial (I hope) question about OID types and
> PostgreSQL. Since PostgreSQL creates tables "WITH OIDS" by default, I'm
> wondering if it is bad practice to allow the default behaviour. For
> example, if I have a database with 60+ tables (all tables have their own
> PK that is not of type OID) and all of them have an OID field created by
> PostgreSQL by default, will this be problematic in the long run? For
> example, if I have 30 tables with records greater than 500,000, will
> PostgreSQL choke?
>
> Thank you in advance for any information you can provide!
>
>
> --
> Amir Khawaja.
>
> ----------------------------------
> Rules are written for those who lack the ability to truly reason, But
> for those who can, the rules become nothing more than guidelines, And
> live their lives governed not by rules but by reason.
> - James McGuigan
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> (... have gone from d-i being barely usable even by its developers
> anywhere, to being about 20% done. Sweet. And the last 80% usually takes
> 20% of the time, too, right?) -- Anthony Towns, debian-devel-announce
