Provide an example showing how to use Lapidus to refresh a PostgreSQL materialized view backed by a mysql_fdw foreign table when a change occurs in the backing table in MySQL.
This pattern creates too much churn and exposed a nasty bug with toast and non-toast tuples in PG core that we're not really too sure about. I do not want to provide a harmful example.
Provide an example showing how to use Lapidus to refresh a PostgreSQL materialized view backed by a mysql_fdw foreign table when a change occurs in the backing table in MySQL.