single table for all vhosts?
Paul Chvostek <[email protected]>
| Newsgroups | gmane.comp.apache.mod-log-sql |
|---|---|
| Message-ID | <[email protected]> |
Hiya. Given the apparant lack of list archives for this list, I'm afraid that as a new user I may be repeating old questions, but anyway ... Should I expect problems if I set every virtualhost to record log entries to the same table, rather than create a new table for each virtualhost? And is there a way to set that table name *once* rather than include a "LogSQLTransferLogTable access_log" in every vhost? I currently have several hundred virtualhosts (and expect it to grow to several thousand shortly), and this is my first foray into mod_log_sql. My current (home-grown) control panel software will of course need to have its functionality extended to support whatever structure I use, and the major thing I'm thinking will be easier to handle in a single-table environment is aging and expiry. I should be able to get all the speed I need with an index on (virtual_host, time_stamp), so I'm wondering what the down side is to going this route. Cancellations would shift from "DROP TABLE www_www_example_com" to "DELETE FROM access_log WHERE virtual_host='www.example.com'". Thoughts? -- Paul Chvostek <[email protected]> Operations / Abuse / Whatever it.canada, hosting and development http://www.it.ca/ __________________________________________________________________ Reminder: to unsubscribe, send email to <[email protected]> with the words "unsubscribe mod_log_sql" in the body (w/o quotes). The module homepage is http://www.grubbybaby.com/mod_log_sql/