Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: [SQL] (Ab)Using schemas and inheritance


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "Tony Wasson" <ajwasson(at)gmail(dot)com>
  • Cc: "Jim C. Nasby" <jnasby(at)pervasive(dot)com>, "Jorge Godoy" <jgodoy(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
  • Subject: Re: [SQL] (Ab)Using schemas and inheritance
  • Date: Tue, 23 May 2006 23:08:58 -0400
  • Message-id: <25040(dot)1148440138(at)sss(dot)pgh(dot)pa(dot)us>

"Tony Wasson" <ajwasson(at)gmail(dot)com> writes:
> $.02 about lots of schemas.

> I worked with an application that had 500 schemas and that worked very
> well. However, as the number of schemas exceeeded 8000 the query speed
> started to degrade. Running \d with a single schema in your search
> path took a few seconds with that many schemas. Queries that were
> running in 100ms were now taking about 600ms.

Note that this probably says more about \d than about anything else.
I can believe that having a large number of schemas listed in your
search path would suck, but there's not a good reason for lots of
schemas unrelated to your session to cause you any great pain.
(\d does some searching that might be impacted by lots of schemas,
but that doesn't say ordinary queries would be.)

If you've got a counterexample please file a bug with details ...

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group