On May 26, 2015, at 1:54 PM, Ravi Krishna <sravikrishna3@xxxxxxxxx> wrote: > > I guess one easy way for large tables is to break it up to small > tables via inheritance and each table assigned to a different > tablespace. That’s also a way you could migrate your current table without disrupting production. Partitioning like that is often done as a performance optimization; but it sounds like you’re proposing that a file system cannot be expected to handle a large table in piece??? I don’t understand that. -- Scott Ribe scott_ribe@xxxxxxxxxxxxxxxx http://www.elevated-dev.com/ https://www.linkedin.com/in/scottribe/ (303) 722-0567 voice -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
