From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: adding more space to the existing server |
Date: | 2019-08-01 04:21:15 |
Message-ID: | 29a4fd4a-4a47-8ca8-faeb-e22fb90ae26c@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/31/19 5:21 PM, Julie Nishimura wrote:
> Hello postgres folks,
>
> We're tossing around the idea of upgrading a replicated postgres cluster
> (37 dbs) by breaking the replication, adding different size (larger) data
> disks to the hot-spare, then turning replication back on, letting it fully
> populate, then breaking replication, making the standby the primary,
> upgrade the disks on the other system, bring it back up, replicate
> backwards until fully replicated then failing-back to the original
> primary. Is this feasible?
>
> Our current size is 22 tb, and it is 97% full
> (PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu
> 5.3.1-14ubuntu2) 5.3.1 20160413, 64-bit)
>
>
> Thank you for your suggestions
Can we correctly infer that you aren't using LVM? (Or in there no more room
on the rack/controller for new drives?)
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Rashmi V Bharadwaj | 2019-08-01 07:10:10 | Cursors for PGJDBC queries |
Previous Message | Julie Nishimura | 2019-07-31 22:21:00 | adding more space to the existing server |