| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Ravi Krishna <sravikrishna3(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: How to expand existing table-space |
| Date: | 2015-05-26 20:11:53 |
| Message-ID: | BEBEF3B8-2A97-4947-B6EA-304749CF6A88@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On May 26, 2015, at 1:54 PM, Ravi Krishna <sravikrishna3(at)gmail(dot)com> 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(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ravi Krishna | 2015-05-26 20:33:49 | Re: How to expand existing table-space |
| Previous Message | Ravi Krishna | 2015-05-26 19:54:29 | Re: How to expand existing table-space |