Re: schema/db design wrt performance

I think FK on every database (oracle and MSSQL too) may hit performance,
but only in DML (insert/update/delete). These are tradeoffs...
referencial integrity vs. problems with batchload for example.
My Oracle experience say when I need to do batchload, I disable
constraints and then apply and work over exceptions.
If you don't make referencial integrity on database maybe you need to do
it on you application... and I think will be very painfull.

--
Fernando O. Papa
DBA


> -----Mensaje original-----
> De: CaptainX0r [mailto:captainx0r@yahoo.com]
> Enviado el: jueves, 16 de enero de 2003 10:52
> Para: pgsql-performance@postgresql.org
> Asunto: [PERFORM] schema/db design wrt performance
>
>
> All,
>
> I just noted in another thread that use of foreign keys in
> postgres significantly hinders performance.  I'm wondering
> what other aspects we should take into consideration in the
> design of our database.  We're coming from Sybase and trying
> to design a more encompassing, modular, generic database that
> won't take a serious performance hit under postgres.
>
> Thanks,
>
> -X
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html