Travis Cline
Travis Cline
watching for schema changes would enable subscribing to tables that are created after initial connection.
The current implementation details use LISTEN/NOTIFY mostly as a development speed optimization. I'd like to explore and implementation that reads WAL data as an alternative.
If we do have an odd failure having postgres logs would be useful.
The last lint run was 3 minutes -- I'm not sure we're getting that much value out of that and we should get it under a minute. refs #55
We can start with number of events by table. Exposing when 8k boundary conditions are met would also probably be useful.