| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org> |
| Subject: | Re: Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER) |
| Date: | 2003-05-20 18:39:03 |
| Message-ID: | 200305201139.03065.josh@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-20 19:03:53 | Re: Removing width from EXPLAIN |
| Previous Message | Tom Lane | 2003-05-20 18:28:42 | Logging (was Re: Suggestion GRANT ALTER, TRIGGER ON ALTER) |