Re: Table Export & Import

2019-04-01 Thread Rene Romero Benavides
Hi Sathish, as Michel Pelletier, pointed out, a trigger based approach (i.e slony-I, bucardo) or the pg_logical plugin (requires server restart) is the way to go, personally, I've worked with slony-I, the initial setup is somewhat tricky, but it works, depending on how transactional the table, stor

Re: Table Export & Import

2019-04-01 Thread Sathish Kumar
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 wrote: > The table size is 160gb. We would like to move/copy this table fro one

Re: Table Export & Import

2019-04-01 Thread Sathish Kumar
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 wrote: > On Mon, Apr 1, 2019 at 7:47 AM Sathish Kumar wrote: > >> Hi Adrian, >> We are exporting live table data to a new database, so we need to

Re: Table Export & Import

2019-04-01 Thread Michel Pelletier
On Mon, Apr 1, 2019 at 7:47 AM Sathish Kumar 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 applicatio

Re: Table Export & Import

2019-04-01 Thread Ron
/"so we need to stop our application until the export/import is completed."/ Why? On 4/1/19 9:47 AM, Sathish Kumar 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 down

Re: Table Export & Import

2019-04-01 Thread Sathish Kumar
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. On Mon, Apr 1, 2019, 10:22 PM Adrian Klaver wrote: > On 3/31/19 11:09 PM, Sathish Kumar wrote: > > Hi Team, > > > > We

Re: Table Export & Import

2019-04-01 Thread Michel Pelletier
As other have pointed out, you can take a pg_dump at anytime. You can provide arguments to pg_dump to only dump a subset of the database (like one table). Also mentioned is using a foreign data wrapper (FDW). yet another approach is to use the "copy to/from program" command to stream the table f

Re: Table Export & Import

2019-04-01 Thread Adrian Klaver
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 addit

Re: Table Export & Import

2019-04-01 Thread Sathish Kumar
Hi Ros, Using server on Cloud. On Mon, Apr 1, 2019, 5:26 PM ROS Didier wrote: > Hi > > One solution could be to use intel technology: FPGA : > https://www.intel.fr/content/www/fr/fr/products/programmable.html > > the principle is to add an PCI electronic card on the server with CPUs and > RAM.

RE: Table Export & Import

2019-04-01 Thread ROS Didier
Hi One solution could be to use intel technology: FPGA : https://www.intel.fr/content/www/fr/fr/products/programmable.html the principle is to add an PCI electronic card on the server with CPUs and RAM. this greatly speeds up the loading of the data into the database. Best Regards [cid:image002.

Re: Table Export & Import

2019-03-31 Thread Andreas Kretschmer
On 1 April 2019 08:09:37 CEST, 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? > >Table Size: 160GB >Postgresql Se