Re: Big number of schemas (3500) into a single database

Hello to everybody again,

thought you didn't hear any news from me for a very long time, the news are
good :-)

I'm still here and promoting PostgreSQL.

I am involved in the developing of a big romanian project for the vets that
will put Linux & PostgreSQL on 3500 computers in the whole country, linked
together with dial-up connections that will keep track of the animal
movements.

The central database (also PostgreSLQ) will hold billions of records with
animal events (births, movements, slaughter and so on) and my question is:

If I will choose to keep a mirror of every workstation database in a
separate schema in the central database that mean that I will have 3500
different schemas.

Is there any limit or any barrier that could stop this kind of approach or
make things go slower?

Constantin Teodorescu

Ancient PgAccess developer

P.S. Please Cc: me at teo(at)flex(dot)ro

"Constantin Teodorescu" <teo(at)flex(dot)ro> writes:
> If I will choose to keep a mirror of every workstation database in a
> separate schema in the central database that mean that I will have 3500
> different schemas.

> Is there any limit or any barrier that could stop this kind of approach or
> make things go slower?

Would you need to put them all into "search_path" at once?

I'm not sure what the scaling issues might be for long search_paths, but
I wouldn't be surprised if it's bad. But as long as you don't do that,
I don't believe there will be any problems.

regards, tom lane

--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escribió:
> "Constantin Teodorescu" <teo(at)flex(dot)ro> writes:
> > If I will choose to keep a mirror of every
> > workstation database in a
> > separate schema in the central database that mean
> > that I will have 3500 different schemas.
>
> > Is there any limit or any barrier that could stop
> > this kind of approach or make things go slower?
>
> Would you need to put them all into "search_path" at
> once?
>
> I'm not sure what the scaling issues might be for
> long search_paths, but I wouldn't be surprised if
> it's bad. But as long as you don't do that,
> I don't believe there will be any problems.
>

if i do a select with fully qualified table names it
will search in the search_path or it will go directly
to the schema?

Just for know.

regards,
Jaime Casanova

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com