Re: BUG #15929: logical decoding can not write down the analyse result when the output file is touched.

From: "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca>
To: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15929: logical decoding can not write down the analyse result when the output file is touched.
Date: 2019-09-25 08:09:46
Message-ID: 2019092516094390916424@highgo.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

hello

There be a problem about pg_recvlogical tool as I described last mail,
and I have made a patch to solve the problem.

It stores the 'st_ino' while opening the output file, and check it when the
process is waked up. It will try to reopen the output file if the output file
stat has changed or disappeared.

What do you think about?

---
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca

Attachment Content-Type Size
pg_recvlogical_problem_20190925.patch application/octet-stream 1.7 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-09-25 12:23:11 BUG #16022: to_json on arrays with unusual lower bound is not intuitive
Previous Message Etsuro Fujita 2019-09-25 07:48:42 Re: BUG #16021: Can create Pk on partitioned table with foreign table as partition