Martijn van Oosterhout <kleptog@xxxxxxxxx> writes: > 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. Another constraint is that many filesystems don't behave real well with lots and lots of files in a single filesystem directory (where "lots and lots" usually translates to trouble in the 10K-100K range). You could work around this to some extent by splitting the database into multiple tablespaces, but most people are going to tell you that a schema with that many tables needs reconsideration anyway. regards, tom lane
