#! /usr/sbin/nft -f | |
# 💀 aka "absolute" firewall for Linux | |
flush ruleset | |
table netdev netdev_rules { | |
chain netdev_filter_ingress_device_lo { | |
type filter hook ingress device lo priority 0 | |
policy drop |
We will add two custom local parameters:
sender_bcc_maps
recipient_bcc_maps
so that we could define our own per-user Bcc: forwarding for all users in a domain (also see this Gist to know more generally about how to configure it for Postfix).
The vacuum full
needs two-times the table size to perform on it because
it first makes full physical copy of the table. If you are running out of
space and in need of reclaiming the space occupated by dead tuples from
a bloated database table but you can not because of lacking free space
in the table's namespace here is how you can work around that (assuming you
some additional disk space resources can be added to the server). It is also
the least disruptive method of doing it (in comparison to the obvious dump
and restore et cetera).
Year | List | Subject: |
Version |
---|---|---|---|
2017 |
pgsql-hackers |
VACUUM and ANALYZE disagreeing on what reltuples means |
<= 10 |
- Niko Matsakis - excellent and must read articles (!)
3x run?! One rights after another?!
zimbra@zimbra:~$ zmprov modifyConfig zimbraMtaMaxMessageSize 1073741824
/opt/zimbra/bin/zmjava: line 59: /bin/java: No such file or directory
zimbra@zimbra:~$ zmprov modifyConfig zimbraMtaMaxMessageSize 1073741824
Killed
zimbra@zimbra:~$ zmprov modifyConfig zimbraMtaMaxMessageSize 1073741824