Postgresql create a core while trying log a message to syslog

Поиск
Список
Период
Сортировка
От Demarest, Jamie
Тема Postgresql create a core while trying log a message to syslog
Дата
Msg-id 3db74722-18cf-44dd-af9a-2575af201b66@CORPMAIL01.corp.sensis.com
обсуждение исходный текст
Ответы Re: Postgresql create a core while trying log a message to syslog  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Postgresql create a core while trying log a message to syslog  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-bugs

 

 

Red Hat Enterprise Linux Server release 7.2 (Maipo)

postgres (PostgreSQL) 9.5.4

 

psql logging has been set up to log to syslog.  When the syslog directory filled up psql trying to log to syslog cause psql to core.

 

Reading symbols from /opt/rh/rh-postgresql95/root/usr/bin/postgres...Reading symbols from /opt/rh/rh-postgresql95/root/usr/bin/postgres...(no debugging symbols found)...done.

(no debugging symbols found)...done.

[New LWP 7949]

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".

Core was generated by `postgres: startup process   recovering 000000050000000000000017      '.

Program terminated with signal 6, Aborted.

#0  0x00007f385ebaf5f7 in raise () from /lib64/libc.so.6

Missing separate debuginfos, use: debuginfo-install rh-postgresql95-postgresql-server-9.5.4-1.el7.x86_64

(gdb) bt

#0  0x00007f385ebaf5f7 in raise () from /lib64/libc.so.6

#1  0x00007f385ebb0ce8 in abort () from /lib64/libc.so.6

#2  0x0000000000797058 in errfinish ()

#3  0x000000000079aa38 in elog_finish ()

#4  0x0000000000495db4 in heap_xlog_update ()

#5  0x000000000049d1af in heap_redo ()

#6  0x00000000004d8117 in StartupXLOG ()

#7  0x00000000006563c2 in StartupProcessMain ()

#8  0x00000000004e4e8a in AuxiliaryProcessMain ()

#9  0x0000000000653800 in StartChildProcess ()

#10 0x0000000000655e44 in PostmasterMain ()

#11 0x0000000000469d3e in main ()

 

Core file can be supplied.

 

Thanks You,

Jamie Demarest

Saab Sensis Corporation

 

 

 


This message is intended only for the addressee and may contain information that is company confidential or privileged. Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Logan Bowers
Дата:
Сообщение: Re: Optimizer Doesn't Push Down Where Expressions on Rollups
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: BUG #16285: bt_metap fails with value is out of range for type integer