[BUGS] Re: BUG #14736: Crash on postgresql server by autovacuum workerprocess

I don't think this could be because of out-of-disk-space.

$ ulimit -a
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 14498
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65000
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 1024
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1      7.8G  3.6G  3.9G  48% /
tmpfs           1.8G     0  1.8G   0% /dev/shm
/dev/xvdb        20G  7.5G   12G  41% /mywork
/dev/xvdc       4.0G  1.7G  2.2G  44% /mnt

The postgres logs just show the below. (Crash happened on 03, July and no
specific logs)
LOG:  database system was shut down at 2017-06-10 00:03:12 GMT
LOG:  MultiXact member wraparound protections are now enabled
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started

Thanks, JOE



--
View this message in context:
http://www.postgresql-archive.org/BUG-14736-Crash-on-postgresql-server-by-autovacuum-worker-process-tp5970386p5970544.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs