> Then you cannot run any queries that extend the size of your relations
> (for example INSERT, UPDATE etc.). Unless you drop your tables or DELETE
> something

Interesting. Well my two cents is don't go any deeper than database.
I.e; don't try and track to the individual relation.

Joshua D. Drake

> The use case for that is the situation when you provide the access to
> different people to do something on the DB. The real world example (in
> which I'm interested) is when the large science project produce a huge
> amount of data, store it in large database, and let different scientists
> work on that data, having their little accounts there. (example
> http://casjobs.sdss.org/CasJobs/Guide.aspx ). That's the way how most of
> large astronomical projects start to work now.
> Regards,
>     Sergey
> *******************************************************************
> Sergey E. Koposov
> Max Planck Institute for Astronomy/Cambridge Institute for
> Astronomy/Sternberg Astronomical Institute
> Tel: +49-6221-528-349
> Web: http://lnfm1.sai.msu.ru/~math
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match


      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

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


Reply via email to