Re: Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER) - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER)
Date
Msg-id 200305201139.03065.josh@agliodbs.com
Whole thread Raw
In response to Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom,

> 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.

I would propose
SELECT
INSERT/UPDATE
DELETE
DDL

> the opportunity to prepare statements in advance of execution.  On the
> other hand, I'm not sure we want three log entries for every command.
> Any thoughts on this out there?

Sorry, I don't know enough about the new structure to have an opinion.

--
-Josh BerkusAglio Database SolutionsSan Francisco



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER)
Next
From: Tom Lane
Date:
Subject: Re: Removing width from EXPLAIN