To me, the issues of scalability come from a management perspective.
I'm dealing with a schema that has tens of thousands of tables, but
they are inherited from a relatively small set of superclass tables.
I imagine there are similar issues to managing schemas as there are to
managing subclass
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> Christopher Browne replied:
>> If you've got tens of thousands of relations, the tab completion code
>> has to draw the whole list of relations from pg_class into memory and
>> "marshal" it into a form usable by GNU Readline.
> Well, it's actuall
Thanks to all who've responded to my concern about scalability with
large numbers of tables. I am reasonably reassured.
I don't really care about the tab-completion speed - it's just that its
slowness was my "heads-up" to the fact that there could be something
related to number of tables to wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phil Endecott wrote:
> For example I find that tab-completion in psql is now unusably slow
...
Christopher Browne replied:
> If you've got tens of thousands of relations, the tab completion code
> has to draw the whole list of relations from pg_clas
Christopher Browne wrote:
Oops! [EMAIL PROTECTED] (Phil Endecott) was seen spray-painting on a wall:
I have a single database with one schema per user. Each user has a
handful of tables, but there are lots of users, so in total the
database has thousands of tables.
If you've got tens of thousands
I'm pretty sure that slowness of tab completion has little to do with
the performance of the filesystems.
If you've got tens of thousands of relations, the tab completion code
has to draw the whole list of relations from pg_class into memory and
"marshal" it into a form usable by GNU Readline. TH
Oops! [EMAIL PROTECTED] (Phil Endecott) was seen spray-painting on a wall:
> Dear Postgresql experts,
>
> I have a single database with one schema per user. Each user has a
> handful of tables, but there are lots of users, so in total the
> database has thousands of tables.
>
> I'm a bit concerned
On Sun, 20 Feb 2005, Phil Endecott wrote:
Dear Postgresql experts,
I have a single database with one schema per user. Each user has a handful
of tables, but there are lots of users, so in total the database has
thousands of tables.
I'm a bit concerned about scalability as this continues to grow
On Sun, 2005-02-20 at 10:45, Lincoln Yeoh wrote:
> I'm not an expert.
>
> Turn off tab completion? It's probably scanning through all the possible
> table names and the algorithm used is probably not designed for that
> number. And with 42000 tables, tab completion may not be that helpful.
>
>
Lincoln Yeoh wrote:
> I'm not an expert.
>
> Turn off tab completion? It's probably scanning through all the
> possible table names and the algorithm used is probably not designed
> for that number. And with 42000 tables, tab completion may not be
> that helpful.
>
> Don't use ext2/ext3? There
I'm not an expert.
Turn off tab completion? It's probably scanning through all the possible
table names and the algorithm used is probably not designed for that
number. And with 42000 tables, tab completion may not be that helpful.
Don't use ext2/ext3? There are other filesystems on Linux which
Dear Postgresql experts,
I have a single database with one schema per user. Each user has a
handful of tables, but there are lots of users, so in total the database
has thousands of tables.
I'm a bit concerned about scalability as this continues to grow. For
example I find that tab-completion
12 matches
Mail list logo