| From: | Alex Balashov <abalashov(at)evaristesys(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Tablespace - PostgreSQL 9.2 |
| Date: | 2016-04-20 23:03:26 |
| Message-ID: | 57180ABE.1090208@evaristesys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 04/20/2016 07:00 PM, drum(dot)lucas(at)gmail(dot)com wrote:
> Setting a WHOLE table to start using tablespace in a different
> array/disks, do I have to have the same on the slaves, right?
No, the tablespace change will be propagated as a DDL change
automatically. What you _do_ have to do manually is to ensure the
physical storage directory for the tablespace(s) exists on both master
and slave.
--
Alex Balashov | Principal | Evariste Systems LLC
1447 Peachtree Street NE, Suite 700
Atlanta, GA 30309
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rajan | 2016-04-21 07:35:03 | Re: Partition table data are not found in the pg_dump backup |
| Previous Message | drum.lucas@gmail.com | 2016-04-20 23:00:12 | Tablespace - PostgreSQL 9.2 |