Search Postgresql Archives

Re: Scalability with large numbers of tables

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux