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 のセマンティクスから始めます。専用接続が必要かどうか、接続の切断をどのように検出するか、信頼できる再接続の指針で何を扱うべきかを確認します。動作と推奨される処理が、明確な例またはテスト済みの実装とともに文書化されていれば完了です。