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: Suggestion GRANT ALTER, TRIGGER ON ALTER |
Date: | 2003-05-20 18:19:36 |
Message-ID: | 200305201119.36988.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom,
> No objection here. We saw a recent request for logging only
> data-modifying statements, too (ie, everything but SELECTs).
> Might be worth thinking about whether those two cases cover it,
> or whether there needs to be some more-general way of choosing
> which statements to log according to their type.
Actually, I can see that ... what about an option like "log_statement" which
took an array of text which would correspond to the first part of the
statement? Then we could leave it up to the DBA do decide what they want to
log, with the validation list being the base list of SQL statements, i.e.:
log_statement = "CREATE TABLE, ALTER TABLE, CREATE VIEW, ALTER VIEW"
--
-Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | greg | 2003-05-20 18:19:53 | Re: Removing width from EXPLAIN |
Previous Message | Tom Lane | 2003-05-20 18:16:57 | Re: Suggestion GRANT ALTER, TRIGGER ON ALTER |