> Strikes me as a tad unwieldy --- the useful cases would correspond to
> very long log_statement lists, and in every new release the list would
> change. It's probably better to have a very small number of categories,
> something like
> SELECT
> INSERT/UPDATE/DELETE
> all DDL
> and be able to flip logging on/off per category. But we need to think
> about exactly what the categories are.
How about 'log to table' like Oracle can (apparently) do. All sorts of
problems I can think with it, but then at least people can just query it
using normal SQL.
Chris
