RE: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication
Date
Msg-id OS7PR01MB183175462A42CCCB15CAF6031F5922@OS7PR01MB18317.jpnprd01.prod.outlook.com
Whole thread
In response to Re: Incorrect CONTEXT reported for errors from parallel apply worker in logical replication  (Zhijie Hou <houzhijie22@gmail.com>)
List pgsql-hackers
Dear Hou,

> But I think we'd better simply save the error context to
> apply_error_context_stack before adding the error callback as that
> looks better than
> indirectly getting the previous one after adding a new one, and it can save
> readers a few cycles. E.g.,

Indeed, PSA the new version.
Also, I adjusted the order of the initialization of DecodingWorker to align with
the location of attributes.

Best regards,
Hayato Kuroda
FUJITSU LIMITED


Attachment

pgsql-hackers by date:

Previous
From: Tender Wang
Date:
Subject: Re: "failed to build any N-way joins" from a five-relation query
Next
From: Takeshi Ideriha
Date:
Subject: Re: Fix doc: explanation of how postgres works when OOM killer is invoked