Re: Documentation update of wal_retrieve_retry_interval to mention table sync worker

On Mon, 13 Jan 2025 at 12:33, vignesh C wrote: > > On Mon, 6 Jan 2025 at 08:47, Peter Smith wrote: > > > > Hi Vignesh, > > > > Some review comments for your v2 patch. > > > > == > > doc/src/sgml/logical-replication.sgml > > > > AFAICT the only difference you made is changing: > > FROM "a spec

Re: Documentation update of wal_retrieve_retry_interval to mention table sync worker

Patch v3-0001 LGTM == Kind Regards, Peter Smith. Fujitsu Australia

Re: Documentation update of wal_retrieve_retry_interval to mention table sync worker

On Mon, 6 Jan 2025 at 08:47, Peter Smith wrote: > > Hi Vignesh, > > Some review comments for your v2 patch. > > == > doc/src/sgml/logical-replication.sgml > > AFAICT the only difference you made is changing: > FROM "a special kind of apply process" > TO "a special kind of table synchronization

Re: Documentation update of wal_retrieve_retry_interval to mention table sync worker

Hi Vignesh, Some review comments for your v2 patch. == doc/src/sgml/logical-replication.sgml 1. The initial data in existing subscribed tables are snapshotted and - copied in a parallel instance of a special kind of apply process. - This process will create its own replic

Re: Documentation update of wal_retrieve_retry_interval to mention table sync worker

On Tue, 31 Dec 2024 at 02:48, Peter Smith wrote: > > On Thu, Dec 26, 2024 at 1:37 AM vignesh C wrote: > > > > Hi, > > > > Currently, we restart the table synchronization worker after the > > duration specified by wal_retrieve_retry_interval following the last > > failure. While this behavior is d

Re: Documentation update of wal_retrieve_retry_interval to mention table sync worker

On Thu, Dec 26, 2024 at 1:37 AM vignesh C wrote: > > Hi, > > Currently, we restart the table synchronization worker after the > duration specified by wal_retrieve_retry_interval following the last > failure. While this behavior is documented for apply workers, it is > not mentioned for table synch

Documentation update of wal_retrieve_retry_interval to mention table sync worker

Hi, Currently, we restart the table synchronization worker after the duration specified by wal_retrieve_retry_interval following the last failure. While this behavior is documented for apply workers, it is not mentioned for table synchronization workers. I believe this detail should be included in

Re: Possible Documentation Update for ALTER STATISTICS

Hi Ahmet, On 11/4/21 14:35, Ahmet Gedemenli wrote: Hey, I've noticed that the current documentation doesn't mention IF EXISTS clause for ALTER STATISTICS in the synopsis section, where PG supports it. https://www.postgresql.org/docs/14/sql-alterstatistics.html

Possible Documentation Update for ALTER STATISTICS

Hey, I've noticed that the current documentation doesn't mention IF EXISTS clause for ALTER STATISTICS in the synopsis section, where PG supports it. https://www.postgresql.org/docs/14/sql-alterstatistics.html (Only for the last item, that is ALTER STATISTICS .. SET STATISTICS; for the others, P

Documentation update

Not sure if this is the correct place to report this, but a colleague and I discovered a problem with the systemd service file as described in the documentation. In the sample, there is a need for a line reading "After=syslogd.target network.target" under the [unit] tag. What we found on Redhat