| From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "Chris Withers *EXTERN*" <chris(at)simplistix(dot)co(dot)uk>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: scaling postgres - can child tables be in a different tablespace? |
| Date: | 2015-08-04 13:14:04 |
| Message-ID: | CANu8FixojJ434v8BJUPMVY_rdegkwKiJ4y1Lnw7Z9oJj794JRQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
As additional advice, to get the best performance, you will want all your
tablespaces to be on separate spindles/disks.
EG: disk1/tblspc1
disk2/tblspc2
disk3/tblspc3
...
disk99/tblspc99
On Tue, Aug 4, 2015 at 5:31 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
wrote:
> Chris Withers wrote:
> > This raises an interesting question: can a child table be in a different
> > tablespace to its parent and other children of that parent?
>
> Yes.
>
> Inheritance is a logical concept and is independent of physical placement.
>
> Yours,
> Laurenz Albe
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-08-04 13:23:24 | Re: Fwd: postgresql databases disappearing and reappearing and disappearing on localhost - Postgresql x649.3 on Windows 8.1 (64) |
| Previous Message | Albe Laurenz | 2015-08-04 09:31:33 | Re: scaling postgres - can child tables be in a different tablespace? |