On Thu, Feb 23, 2006 at 11:21:33AM -0800, Jon Cruz wrote: > > > Thanks. Yeah, I actually *did* do a search of the archives, as well as > Google, but I'm only finding the size limitations (and everything else). > > I'm looking for the number of actual tables a server can handle. And > the number of databases. > > My gut feeling is "unlimited" (like everything else)... Logically, unlimited. Practically, because tables are stored as files, at some point you might run out of inodes on your disk. You're more likely to run out of disk-space first though, unless your tables are small. More directly, as the number of tables grow, so does the size of the system catalogs. So this will show up as increased planning time. Databases are just a way of dividing up tables. No strict limit, but the number-of-files thing applies. Actually, it's tables-per-database that's the relevent to planning time, as the backend doesn't need to worry about tables in other databases. Hope this helps, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Attachment:
signature.asc
Description: Digital signature
