| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | teo(at)flex(dot)ro |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Big number of schemas (3500) into a single database |
| Date: | 2004-11-24 05:32:42 |
| Message-ID: | 4293.1101274362@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
"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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2004-11-24 05:46:54 | Re: How to make @id or $id as parameter name in plpgsql, is it available? |
| Previous Message | Barry Lind | 2004-11-24 05:15:32 | Re: [JDBC] Strange server error with current 8.0beta driver |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2004-11-24 05:40:43 | Re: Slow execution time when querying view with WHERE clause |
| Previous Message | Bruce Momjian | 2004-11-24 04:38:58 | Re: scalability issues on win32 |