The limit for dbclean is now configurable
This commit is contained in:
parent
49c7b5481b
commit
c4cc7a4afb
2 changed files with 8 additions and 3 deletions
|
@ -121,9 +121,14 @@ db_loglimit_index_high = 0
|
|||
|
||||
; dbclean_expire_conversation (Integer)
|
||||
; When DBClean is enabled, any entry in the conversation table will be deleted after this many days.
|
||||
; These data are normally needed only for debugging purposes and they are safe to delete.
|
||||
: This data is used for ActivityPub, so it shouldn't be lower than the average duration of a discussion.
|
||||
dbclean_expire_conversation = 90
|
||||
|
||||
; dbclean-expire-limit (Integer)
|
||||
; This defines the number of items that are to be deleted in a single call.
|
||||
; Reduce this value when you are getting memory issues.
|
||||
dbclean-expire-limit = 1000
|
||||
|
||||
; diaspora_test (Boolean)
|
||||
; For development only. Disables the message transfer.
|
||||
diaspora_test = false
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue