| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
| Cc: | Phil Endecott <spam_from_postgresql_general(at)chezphil(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Scalability with large numbers of tables |
| Date: | 2005-02-20 20:31:02 |
| Message-ID: | 1108931462.30529.52.camel@state.g2switchworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
>
> Don't use ext2/ext3? There are other filesystems on Linux which perform
> decently with thousands of files in a directory. AFAIK ext2 and ext3 don't
> allow you to have single large files anyway - also not sure if postgresql
> BLOBs will hit those filesystem limits or postgresql splits BLOBs or hits
> its own limits first - I'd just store multi-GB stuff out of the DB.
Actually, while ext2/3 used to be pretty pokey with a large number of
files, the latest version seems quite comfortable handling tens of
thousands with a fairly good response time.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonel Rienton | 2005-02-20 20:41:14 | Re: PGSQL 8.0.1 Win 2K Installation Problem |
| Previous Message | Phil Endecott | 2005-02-20 19:30:33 | Re: Triggers, again.. ;-) |