Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fbRuE-0006Cb-L2 for pgsql-admin@arkaria.postgresql.org; Fri, 06 Jul 2018 14:40:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fbRuC-0005d9-6O for pgsql-admin@arkaria.postgresql.org; Fri, 06 Jul 2018 14:40:16 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fbRuB-0005cF-Ms for pgsql-admin@lists.postgresql.org; Fri, 06 Jul 2018 14:40:16 +0000 Received: from himalaya.serversfarm.com ([173.254.202.145] helo=rio.serversfarm.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fbRu4-0005Nf-Q3 for pgsql-admin@postgresql.org; Fri, 06 Jul 2018 14:40:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ibosstech-us.com; s=default; h=Content-Type:Mime-Version:Reply-To: References:In-Reply-To:Message-Id:Date:Subject:To:From:Sender:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=s4LM8Hj/suz1U5zSFgav2R+AC9Ku+L40xWcPSBh+5eM=; b=dJztBLOt/HDH38OG1heLlPycQ sihg+i74T3QswGXOEPihFoQMOMc1aAsFvzTLnaGBrU3FvnLs7i7QDtciiVPJtRKkjS/deRep/Qm4s kBjZTi82ixnvTQB+7CNB0uw82p60Hhron+K54ImT23ce2/6sXsu15lI9xh3EHwoIg8qSOHNR8/JWh 6s0n1Qsxu501XNAUI8UxPqBeEoXpIkEY9npUK7j7Ej4ChB9GKqV9rl06xk9Faq4jTJdQFq6woLmIm f3H6R0R8M2n2ldQTRedGKWkiDi1Ek2CihpBwB8OjjS/GD3sVtt/rB7pETQwrOXUBz9nSzgK6pfxox T8LUxnEow==; Received: from [111.93.60.54] (port=57674 helo=[192.168.3.137]) by rio.serversfarm.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1fbRu4-00GKu2-Fi for pgsql-admin@postgresql.org; Fri, 06 Jul 2018 10:40:09 -0400 From: "Anjul Tyagi" To: pgsql-admin@postgresql.org Subject: Re: logical Replication Date: Fri, 06 Jul 2018 14:40:05 +0000 Message-Id: In-Reply-To: References: Reply-To: "Anjul Tyagi" User-Agent: eM_Client/7.1.31849.0 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MBA0CBB00A-C38D-43B0-88B9-739D8EA126DD" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rio.serversfarm.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ibosstech-us.com X-Get-Message-Sender-Via: rio.serversfarm.com: authenticated_id: anjul@ibosstech-us.com X-Authenticated-Sender: rio.serversfarm.com: anjul@ibosstech-us.com X-Source: X-Source-Args: X-Source-Dir: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --------=_MBA0CBB00A-C38D-43B0-88B9-739D8EA126DD Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable Liu, I believe they have restriction for large object like BLOB. When i read=20 the other details, there are no limitation for large amount of data. Regards, Anjul TYAGI =C3=BC Go Green ------ Original Message ------ From: "Liu Huarong" To: anjul@ibosstech-us.com Cc: pgsql-admin@postgresql.org Sent: 06-07-2018 13:02:09 Subject: Re: logical Replication >Have you checked these restrictions? >https://www.postgresql.org/docs/10/static/logical-replication-restrictions= .html > > >Anjul Tyagi =E4=BA=8E2018=E5=B9=B47=E6=9C=886=E6= =97=A5=E5=91=A8=E4=BA=94 =E4=B8=8B=E5=8D=883:11=E5=86=99=E9=81=93=EF=BC=9A >>Team, >> >>we are trying to setup an logical replication on the Postgres 10.4, we=20 >>are able to replicate the small tables but facing issue with big=20 >>tables, when table has around 60 columns and 30 million rows. >> >>While checking the log on publication server, it shows copy command=20 >>but did not copy data to subscriber server. >> >>Postgres Version - 10.4 >>Linux - SUSE SLE-12.3 >> >>Following are the setting we have enabled on Primary server: >> >>Primary Server: >>wal_level =3D logical >>shared_buffers =3D 6GB >>effective_cache_size =3D 18GB >>maintenance_work_mem =3D 1536MB >>checkpoint_completion_target =3D 0.9 >>wal_buffers =3D 16MB >>default_statistics_target =3D 100 >>random_page_cost =3D 1.1 >>effective_io_concurrency =3D 200 >>work_mem =3D 3145kB >>min_wal_size =3D 1GB >>max_wal_size =3D 2GB >>max_replication_slots =3D 25 >>max_wal_senders =3D 30 >>max_parallel_workers_per_gather =3D 2 >>max_parallel_workers =3D 4 >> >>Secondary Server: >>shared_buffers =3D 6GB >>effective_cache_size =3D 18GB >>maintenance_work_mem =3D 1536MB >>checkpoint_completion_target =3D 0.9 >>wal_buffers =3D 16MB >>default_statistics_target =3D 100 >>random_page_cost =3D 1.1 >>effective_io_concurrency =3D 200 >>work_mem =3D 3145kB >>max_replication_slots =3D 25 >>max_logical_replication_workers =3D 30 >>max_worker_processes =3D 31 >> >>can you please help us to understand, if is there any issue on the=20 >>configuration. >> >> >>Regards, >> >>Anjul TYAGI >> >> >> >>=C3=BC Go Green >> >> --------=_MBA0CBB00A-C38D-43B0-88B9-739D8EA126DD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Liu,

I believe they have restriction for large object like BL= OB. When i read the other details, there are no limitation for large amount = of data.

=C2=A0
=C2=A0=C2=A0
=
=C2=A0
=C2=A0

Regards,

Anjul TYAGI

=C2=A0

=C3=BC<= /b>=C2=A0Go=C2= =A0Green


------ Original Message ------
From: "Liu Huarong" <liu= huarongynu@gmail.com>
Sent: 06-07-2018 13:02:09
Subject: Re: logical Replication


Anjul Tyagi <anjul@ibosstech-us.com> =E4=BA=8E2018=E5=B9=B47=E6=9C=886=E6=97=A5= =E5=91=A8=E4=BA=94 =E4=B8=8B=E5=8D=883:11=E5=86=99=E9=81=93=EF=BC=9A
<= /div>
Team,

we are trying to setup an logica= l replication on the Postgres 10.4, we are able to replicate the small tabl= es but facing issue with big tables, when table has around 60 columns and 3= 0 million rows.=C2=A0

While checking the log on= publication server, it shows copy command but did not copy data to subscrib= er server.=C2=A0

Postgres Version - 10.4
Linux - SUSE SLE-12.3

Following are the setti= ng we have enabled on Primary server:

Primary = Server:
wal_level =3D logical
shared_buffers =3D 6= GB
effective_cache_size =3D 18GB
maintenance_work_mem = =3D 1536MB
checkpoint_completion_target =3D 0.9
wal_bu= ffers =3D 16MB
default_statistics_target =3D 100
random= _page_cost =3D 1.1
effective_io_concurrency =3D 200
wor= k_mem =3D 3145kB
min_wal_size =3D 1GB
max_wal_size =3D= 2GB
max_replication_slots =3D 25<= /span>
max_wal_senders =3D 30=
max_parallel= _workers_per_gather =3D 2
max_parallel_workers =3D 4

Secondary Ser= ver:
shared_buffers =3D 6GB
effe= ctive_cache_size =3D 18GB
maintenance_work_mem =3D 1536MB
checkpoint_completion_target =3D 0.9
wal_buffers =3D 16MB
default_statistics_target =3D 100
random_page_cost =3D 1.1<= /div>
effective_io_concurrency =3D 200
work_mem =3D 3145kB
max_replication_slots =3D 25=C2=A0
max_logical_replicatio= n_workers =3D 30
max_worker_processes =3D 31

can you please help us to understand, if is there any issue on the c= onfiguration.
=C2=A0
=C2=A0

Regards= ,

Anjul <= b>TYAGI

=C2= =A0

=C3=BC=C2=A0Go=C2=A0Green


--------=_MBA0CBB00A-C38D-43B0-88B9-739D8EA126DD--