2ndQuadrant / pglogical

Logical Replication extension for PostgreSQL 15, 14, 13, 12, 11, 10, 9.6, 9.5, 9.4 (Postgres), providing much faster replication than Slony, Bucardo or Londiste, as well as cross-version upgrades.

Home Page:http://2ndquadrant.com/en/resources/pglogical/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Apply Errors are Not logged when using AWS RDS Postgres

kkr2320 opened this issue · comments

Using PGLogical extension ( version 2.4.1) in AWS RDS Postgres Version 14.5.

On testing a error handling scenario, the RDS postgres error log only contains a single line
"2023-01-20 02:14:37 UTC::@:[367]:LOG: 00000: background worker "pglogical apply 16402:1901723755" (PID 25301) exited with exit code 1" .

There are no additional details logged about the error. In our case , we are expecting an missing column on the target database. Without any details about error , it becomes an extreme wild chase to fix the errors and resume replication.

Questions -
How to enable a verbose logging for PGLogical error situations when using AWS RDS Postgres. ?
How does the logging works on non RDS Postgres implementation ?

Any help figuring this out would be greatly appreciated..

v/R

Below the RDS Postgres parameters to enable highest level of logging. Yet background Pglogical worker NOT registering any SQL errors or any errors relating to underlying table.

log_error_verbosity = verbose
log_min_duration_sample = 0
log_min_duration_statement = 0
log_min_error_statement = debug5
log_min_messages = debug5
log_replication_commands = 1
log_statement = all

Is there is an another way to replay the transaction in the command line ( or foreground) and get out more details .. ?

Folks - Any update on this issue ..? Is this something can be on the roadmap , if its current behavior. ?