From: | Sathish Kumar <satcse88(at)gmail(dot)com> |
---|---|
To: | Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Table Export & Import |
Date: | 2019-04-02 02:22:58 |
Message-ID: | CANa_DOjhK_=BTc+4+_eZ6iQ6tqGTPDH+LSme5w-Z2Jr1ACz3Mw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi All,
Can you tell me a way for table replication or sync or to achieve minimal
downtime from dbserver1 to dbserver2 on Postgresql 9.5
Table Size: 160gb
4VCPU, 16gb RAM
On Tue, Apr 2, 2019, 12:19 AM Sathish Kumar <satcse88(at)gmail(dot)com> wrote:
> The table size is 160gb. We would like to move/copy this table fro one db
> server to another db server.
>
> On Tue, Apr 2, 2019, 12:17 AM Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com>
> wrote:
>
>> On Mon, Apr 1, 2019 at 7:47 AM Sathish Kumar <satcse88(at)gmail(dot)com> wrote:
>>
>>> Hi Adrian,
>>> We are exporting live table data to a new database, so we need to stop
>>> our application until the export/import is completed. We would like to
>>> minimise this downtime.
>>>
>>
>> It's more complicated if you want to keep your application running and
>> writing to the db while migrating. There are trigger-level replication
>> tools, like slony that can be used to stream changes to the new database,
>> and then you switch over once you get both of them to parity, but there are
>> some gotchas. You said the db is only 160GB, it depend a lot on what kind
>> of schema we're talking about, but I imagine it wouldn't take long to just
>> take the downtime and do a normal pg_upgrade.
>>
>>
>>>
>>> On Mon, Apr 1, 2019, 10:22 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
>>> wrote:
>>>
>>>> On 3/31/19 11:09 PM, Sathish Kumar wrote:
>>>> > Hi Team,
>>>> >
>>>> > We have a requirement to copy a table from one database server to
>>>> > another database server. We are looking for a solution to achieve
>>>> this
>>>> > with lesser downtime on Prod. Can you help us with this?
>>>>
>>>> So what is creating the downtime now?
>>>>
>>>> In addition to other suggestions you might want to take a look at:
>>>>
>>>> https://www.postgresql.org/docs/9.5/postgres-fdw.html
>>>>
>>>>
>>>> >
>>>> > Table Size: 160GB
>>>> > Postgresql Server Version: 9.5
>>>> >
>>>> >
>>>>
>>>>
>>>> --
>>>> Adrian Klaver
>>>> adrian(dot)klaver(at)aklaver(dot)com
>>>>
>>>
From | Date | Subject | |
---|---|---|---|
Next Message | Rene Romero Benavides | 2019-04-02 03:20:33 | Re: stale WAL files? |
Previous Message | 김준형 | 2019-04-02 01:21:24 | Postgresql with nextcloud in Windows Server |