One thing that can be useful is to check which tables are big. If it's
logging table, try disabling RCPatrolling (or upgrading to 1.32 so it
doesn't log autopatrol actions). If it's revision table, upgrading might
help with actor table migration and then you just set it to "write new/read
new" so i
I agree with John, it would be interesting to know the sizes of the various
tables. While 1 GB is a relatively small limit for a DB, its still a lot of
space for a small wiki (I think you can find how big different tables are
via
https://stackoverflow.com/questions/9620198/how-to-get-the-sizes-of-t
Might also look at what is using your space and see if it can be optimized.
On Thu, Dec 27, 2018 at 12:51 PM Brett Langston <
brett.langs...@tiscali.co.uk> wrote:
> Thanks for the suggestions. By deleting the cache tables, and the oldest
> entries from the logging table, I've been able to reduce
Thanks for the suggestions. By deleting the cache tables, and the oldest
entries from the logging table, I've been able to reduce the size to below 1GB
and get back control of the wiki for now. It looks like I need to find an ISP
with more hosting space in the longer term though.
Cheers,
Bret
I would actually consider using another host -- one that would have
the decency to make an exception and let your DB go past 1 GB for just
one day so that you could reduce its size.
Beyond that, however, you could consider exporting some data in SQL
format, like the user table, for example, and th
You can empty the ‘objectcache’ table. Data in it will be computed again
when needed. Note that doing this may also cause all users to get logged
out, depending on your wiki configuration.
--
Matma Rex
___
MediaWiki-l mailing list
To unsubscribe, go to:
Hi everyone,
I'm using MW version 1.29.2 on a shared hosting server (PHP 7.2.13 and MySQL
5.5.60). I've inadvertently exceeded the ISP's 1GB size limit of the database,
with the result that I can't make any further changes. The wiki is still up and
running, but I can't edit or delete content,