summaryrefslogtreecommitdiff
path: root/database/database.pgsql
diff options
context:
space:
mode:
authorDries Buytaert <dries@buytaert.net>2005-04-11 19:05:52 +0000
committerDries Buytaert <dries@buytaert.net>2005-04-11 19:05:52 +0000
commite3d62d907b07dbace7404fb378a97e8d38cf1e9e (patch)
tree590c126f6dbb469ebae8022769f926115dc6602c /database/database.pgsql
parentd0d5b52ac1f1248b43da892621ce2c46af4fedcc (diff)
downloadbrdo-e3d62d907b07dbace7404fb378a97e8d38cf1e9e.tar.gz
brdo-e3d62d907b07dbace7404fb378a97e8d38cf1e9e.tar.bz2
- Patch #19298 by Jeremy: loose caching!
Drupal's existing caching mechanism doesn't perform well on highly dynamic websites in which the cache is flushed frequently. One example is a site that is under attack by a spambot that is posting spam comments every few seconds, causing all cached pages to be flushed every few seconds. Loose caching immediately flushes the cache only for specific users who have modified cached data (whether or not they are logged in), delaying the flushing of data for other users by several minutes. (I rewrote the help text a bit and made minor changes to the code comments.)
Diffstat (limited to 'database/database.pgsql')
-rw-r--r--database/database.pgsql1
1 files changed, 1 insertions, 0 deletions
diff --git a/database/database.pgsql b/database/database.pgsql
index 64a63215d..a911049f0 100644
--- a/database/database.pgsql
+++ b/database/database.pgsql
@@ -587,6 +587,7 @@ CREATE TABLE sessions (
sid varchar(32) NOT NULL default '',
hostname varchar(128) NOT NULL default '',
timestamp integer NOT NULL default '0',
+ cache integer NOT NULL default '0',
session text,
PRIMARY KEY (sid)
);