NOTIFY/LISTEN and connection loss

I need to watch data changes in multiple tables. One option is to add triggers and log changes to another table, which can be polled by the app every few seconds. A better option is to send PG notifications and set up a handler using conn.add_listener(). Do I need a dedicated connection for this approach, as opposed to a connection pool? How should I handle connection loss? If I kill a PG server process, asyncpg won't notice it either until TCP timeout (which can be very long) or until I try to execute another SQL command using the same connection object. Can you please provide a code snippet or a hint how to work with PG notifications more reliably?

从 asyncpg 的 conn.add_listener() 行为以及 PostgreSQL LISTEN/NOTIFY 在连接丢失时的语义入手。确定是否需要专用连接、如何检测连接丢失，以及可靠的重新连接指导应涵盖哪些内容。当行为和建议的处理方式通过清晰的示例或经过测试的实现得到记录时，即视为完成。