From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, nolan(at)celery(dot)tssi(dot)com, Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] Physical Database Configuration |
Date: | 2003-07-19 03:06:36 |
Message-ID: | 1058583995.55079.15.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> Another good reason for per-database directories under the tablespace is
> to prevent directories from containing too many files.
Actually, I would take that as an reason not to have database
directories.
If the number of files becomes a concern, we would need some kind of a
hashing algorithm to disperse them appropriately. The database
directory would just get in the way without really adding anything. Is
1000 per files as a directory limit still the rule of thumb for a limit?
A single TB sized db would start to run into those types of limits.
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2003-07-19 03:19:47 | Re: [GENERAL] Physical Database Configuration |
Previous Message | Bruce Momjian | 2003-07-19 02:54:15 | Re: [GENERAL] Physical Database Configuration |
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2003-07-19 03:19:47 | Re: [GENERAL] Physical Database Configuration |
Previous Message | Oleg Bartunov | 2003-07-19 02:58:07 | Re: commiters log |