안녕하세요. 서버는 window2002 를 사용하고, postgresql 9.3인데 PG가 종종 내려갑니다.
log를 봐도 뭐가 문제인지 모르겠네요.
아래는 pg_log의 내용입니다.
==========================================================
2017-02-10 01:52:12 KST:::1(61769):jpsuser:@logms:[849096]: FATAL: canceling authentication due to timeout
2017-02-10 02:28:26 KST:::1(61829):jpsuser:@logms:[1942736]: FATAL: canceling authentication due to timeout
2017-02-10 02:31:29 KST:::1(61773):jpsuser:@logms:[252552]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 02:47:41 KST:::1(62831):jpsuser:@logms:[1258324]: FATAL: canceling authentication due to timeout
2017-02-10 02:47:41 KST:::1(62823):jpsuser:@logms:[1159356]: FATAL: canceling authentication due to timeout
2017-02-10 02:56:00 KST:::1(62924):jpsuser:@logms:[1155120]: FATAL: canceling authentication due to timeout
2017-02-10 02:56:00 KST:::1(62925):jpsuser:@logms:[831196]: FATAL: canceling authentication due to timeout
2017-02-10 02:56:02 KST:::1(62929):jpsuser:@logms:[325448]: FATAL: canceling authentication due to timeout
2017-02-10 02:56:03 KST:::1(62931):jpsuser:@logms:[1789996]: FATAL: canceling authentication due to timeout
2017-02-10 03:37:57 KST:::1(62923):jpsuser:@logms:[1906168]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 03:37:57 KST:::1(62830):jpsuser:@logms:[1146560]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 03:37:57 KST:::1(62827):jpsuser:@logms:[1688556]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 03:37:57 KST:::1(62820):jpsuser:@logms:[896728]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 03:38:40 KST:::1(62930):jpsuser:@logms:[1239224]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 03:38:40 KST:::1(62928):jpsuser:@logms:[690072]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 05:04:48 KST:::1(64025):jpsuser:@logms:[6664]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 05:47:37 KST:::1(65109):jpsuser:@logms:[299636]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 06:59:04 KST:::1(65245):jpsuser:@logms:[350764]: PANIC: could not write to log file 818, segment 76 at offset 2727936, length 8192: Invalid argument
2017-02-10 07:00:13 KST:::@:[969356]: LOG: CreateProcess call failed: A blocking operation was interrupted by a call to WSACancelBlockingCall.
(error code 299)
2017-02-10 07:00:13 KST:::@:[969356]: LOG: could not fork autovacuum worker process: A blocking operation was interrupted by a call to WSACancelBlockingCall.
2017-02-10 07:00:13 KST:::@:[969356]: LOG: server process (PID 350764) exited with exit code 3
2017-02-10 07:00:13 KST:::@:[969356]: DETAIL: Failed process was running: UPDATE EPI$SCHEDULER_JOBS SET NEXT_START_TIME = TO_TIMESTAMP($1, 'YYYYMMDDHH24MISS'), LAST_START_TIME = TO_TIMESTAMP($2, 'YYYYMMDDHH24MISS'), LAST_END_TIME = TO_TIMESTAMP($3, 'YYYYMMDDHH24MISS') WHERE INST_NO = $4 AND PGM_NAME = $5 AND PGM_ACTION = $6
2017-02-10 07:00:13 KST:::@:[969356]: LOG: terminating any other active server processes
2017-02-10 07:00:32 KST:::1(58809):jpsuser:@logms:[281936]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:33 KST:::1(58824):jpsuser:@logms:[1139196]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:33 KST:::1(60265):jpsuser:@logms:[1452256]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:34 KST:::1(63171):jpsuser:@logms:[508964]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:34 KST:::1(62031):jpsuser:@logms:[1960888]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:34 KST:::1(58830):jpsuser:@logms:[339816]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:34 KST:::1(58837):jpsuser:@logms:[1610608]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(63170):jpsuser:@logms:[2720]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:34 KST:::1(58836):jpsuser:@logms:[95316]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(63976):jpsuser:@logms:[1874892]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(58833):jpsuser:@logms:[91164]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:34 KST:::1(58841):jpsuser:@logms:[219424]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(62033):jpsuser:@logms:[1486624]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(62025):jpsuser:@logms:[1463320]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(58842):jpsuser:@logms:[438880]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(62032):jpsuser:@logms:[1349276]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:35 KST:::1(63141):jpsuser:@logms:[1081356]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:36 KST:::1(60111):jpsuser:@logms:[1310124]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:36 KST:::1(63976):jpsuser:@logms:[1874892]: LOG: could not send data to client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:36 KST:::1(63976):jpsuser:@logms:[1874892]: FATAL: connection to client lost
2017-02-10 07:00:36 KST:::1(60269):jpsuser:@logms:[298428]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:37 KST:::1(63172):jpsuser:@logms:[1558064]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:37 KST:::1(63172):jpsuser:@logms:[1558064]: LOG: could not send data to client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:37 KST:::1(63172):jpsuser:@logms:[1558064]: FATAL: connection to client lost
2017-02-10 07:00:36 KST:::1(63177):jpsuser:@logms:[1778952]: LOG: could not send data to client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:37 KST:::1(63177):jpsuser:@logms:[1778952]: FATAL: connection to client lost
2017-02-10 07:00:38 KST:::1(62050):jpsuser:@logms:[321664]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:37 KST:::1(60278):jpsuser:@logms:[516528]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:37 KST:::1(63164):jpsuser:@logms:[721708]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:38 KST:::1(63168):jpsuser:@logms:[842660]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:38 KST:::1(62029):jpsuser:@logms:[1722412]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:38 KST:::1(62014):jpsuser:@logms:[971772]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:39 KST:::1(61467):jpsuser:@logms:[1592620]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:41 KST:::1(61458):jpsuser:@logms:[485192]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:41 KST:::1(61498):jpsuser:@logms:[315872]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:48 KST:::1(58844):jpsuser:@logms:[730684]: LOG: could not send data to client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:48 KST:::1(58844):jpsuser:@logms:[730684]: STATEMENT: COMMIT
2017-02-10 07:00:50 KST:::1(58838):jpsuser:@logms:[383028]: LOG: could not send data to client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:50 KST:::1(58838):jpsuser:@logms:[383028]: STATEMENT: COMMIT
2017-02-10 07:00:51 KST:::1(58817):jpsuser:@logms:[116868]: LOG: could not send data to client: No connection could be made because the target machine actively refused it.
2017-02-10 07:00:51 KST:::1(58817):jpsuser:@logms:[116868]: STATEMENT: COMMIT
2017-02-10 07:01:05 KST:10.229.4.222(54111):jpsuser:@logms:[1801960]: FATAL: the database system is in recovery mode
2017-02-10 07:01:05 KST:::1(53596):[unknown]:@[unknown]:[424180]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53596):[unknown]:@[unknown]:[424180]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53575):[unknown]:@[unknown]:[737784]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53575):[unknown]:@[unknown]:[737784]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53531):[unknown]:@[unknown]:[870744]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53526):[unknown]:@[unknown]:[696460]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53531):[unknown]:@[unknown]:[870744]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53526):[unknown]:@[unknown]:[696460]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53567):[unknown]:@[unknown]:[691736]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53567):[unknown]:@[unknown]:[691736]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53568):[unknown]:@[unknown]:[1184876]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53568):[unknown]:@[unknown]:[1184876]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53594):[unknown]:@[unknown]:[1200788]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53594):[unknown]:@[unknown]:[1200788]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53580):[unknown]:@[unknown]:[1424584]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53576):[unknown]:@[unknown]:[1952880]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53580):[unknown]:@[unknown]:[1424584]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53576):[unknown]:@[unknown]:[1952880]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53578):[unknown]:@[unknown]:[147304]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53578):[unknown]:@[unknown]:[147304]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53534):[unknown]:@[unknown]:[982664]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53534):[unknown]:@[unknown]:[982664]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53536):[unknown]:@[unknown]:[408516]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53536):[unknown]:@[unknown]:[408516]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53595):[unknown]:@[unknown]:[1195896]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53595):[unknown]:@[unknown]:[1195896]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53561):[unknown]:@[unknown]:[907060]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53561):[unknown]:@[unknown]:[907060]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53579):[unknown]:@[unknown]:[413132]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53579):[unknown]:@[unknown]:[413132]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53499):[unknown]:@[unknown]:[1532336]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53499):[unknown]:@[unknown]:[1532336]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53559):[unknown]:@[unknown]:[697864]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53559):[unknown]:@[unknown]:[697864]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53566):[unknown]:@[unknown]:[1402916]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53566):[unknown]:@[unknown]:[1402916]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:10.222.7.143(62954):jpsuser:@logms:[877396]: FATAL: the database system is in recovery mode
2017-02-10 07:01:05 KST:::1(53592):[unknown]:@[unknown]:[1098360]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53592):[unknown]:@[unknown]:[1098360]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53522):[unknown]:@[unknown]:[1832136]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53522):[unknown]:@[unknown]:[1832136]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53535):[unknown]:@[unknown]:[339116]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53535):[unknown]:@[unknown]:[339116]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53527):[unknown]:@[unknown]:[1716756]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53527):[unknown]:@[unknown]:[1716756]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53562):[unknown]:@[unknown]:[1195572]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53562):[unknown]:@[unknown]:[1195572]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53509):[unknown]:@[unknown]:[1915400]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53509):[unknown]:@[unknown]:[1915400]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53597):[unknown]:@[unknown]:[626556]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53597):[unknown]:@[unknown]:[626556]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:::1(53565):[unknown]:@[unknown]:[158100]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 07:01:05 KST:::1(53565):[unknown]:@[unknown]:[158100]: LOG: incomplete startup packet
2017-02-10 07:01:05 KST:10.229.4.222(54112):jpsuser:@logms:[1801816]: FATAL: the database system is in recovery mode
2017-02-10 07:01:05 KST:10.222.7.143(62955):jpsuser:@logms:[1531568]: FATAL: the database system is in recovery mode
2017-02-10 07:01:05 KST:10.229.4.222(54113):jpsuser:@logms:[1924752]: FATAL: the database system is in recovery mode
2017-02-10 07:01:05 KST:10.222.7.143(62956):jpsuser:@logms:[505368]: FATAL: the database system is in recovery mode
2017-02-10 07:01:05 KST:10.229.4.222(54114):jpsuser:@logms:[683716]: FATAL: the database system is in recovery mode
2017-02-10 07:01:05 KST:10.222.7.143(62957):jpsuser:@logms:[33872]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54115):jpsuser:@logms:[554132]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62958):jpsuser:@logms:[299620]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62960):jpsuser:@logms:[377292]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54116):jpsuser:@logms:[1655372]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54117):jpsuser:@logms:[1065424]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62961):jpsuser:@logms:[583400]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54118):jpsuser:@logms:[609608]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62962):jpsuser:@logms:[889248]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54119):jpsuser:@logms:[1923312]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62963):jpsuser:@logms:[786608]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54120):jpsuser:@logms:[626540]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62964):jpsuser:@logms:[1240924]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54121):jpsuser:@logms:[1591904]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62965):jpsuser:@logms:[869668]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62966):jpsuser:@logms:[1410780]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54122):jpsuser:@logms:[1848740]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.229.4.222(54123):jpsuser:@logms:[1366916]: FATAL: the database system is in recovery mode
2017-02-10 07:01:06 KST:10.222.7.143(62967):jpsuser:@logms:[272248]: FATAL: the database system is in recovery mode
2017-02-10 07:02:05 KST:::@:[969356]: LOG: all server processes terminated; reinitializing
2017-02-10 07:02:16 KST:::@:[969356]: FATAL: pre-existing shared memory block is still in use
2017-02-10 07:02:16 KST:::@:[969356]: HINT: Check if there are any old server processes still running, and terminate them.
2017-02-10 10:06:44 KST:::1(53824):jpsuser:@logms:[1167748]: FATAL: the database system is starting up
2017-02-10 10:06:44 KST:10.229.4.222(57373):jpsuser:@logms:[702244]: FATAL: the database system is starting up
2017-02-10 10:06:44 KST:::1(53825):OTP-DBMON$:@postgres:[1731680]: FATAL: the database system is starting up
2017-02-10 10:06:44 KST:10.229.4.222(57374):jpsuser:@logms:[59684]: FATAL: the database system is starting up
2017-02-10 10:06:44 KST:::@:[1728272]: LOG: database system was not properly shut down; automatic recovery in progress
2017-02-10 10:06:44 KST:10.229.4.222(57375):jpsuser:@logms:[505044]: FATAL: the database system is starting up
2017-02-10 10:06:44 KST:10.229.4.222(57376):jpsuser:@logms:[691552]: FATAL: the database system is starting up
2017-02-10 10:06:44 KST:10.229.4.222(57377):jpsuser:@logms:[1778740]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:::@:[1728272]: LOG: redo starts at 332/4839D458
2017-02-10 10:06:45 KST:10.229.4.222(57378):jpsuser:@logms:[1872248]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57379):jpsuser:@logms:[769044]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57380):jpsuser:@logms:[1731332]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57381):jpsuser:@logms:[547684]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57382):jpsuser:@logms:[1622864]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57383):jpsuser:@logms:[274664]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57384):jpsuser:@logms:[1305816]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:::1(53826):OTP-DBMON$:@postgres:[1982804]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57385):jpsuser:@logms:[167816]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57386):jpsuser:@logms:[1151496]: FATAL: the database system is starting up
2017-02-10 10:06:45 KST:10.229.4.222(57387):jpsuser:@logms:[612540]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57388):jpsuser:@logms:[307356]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57389):jpsuser:@logms:[1951968]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57390):jpsuser:@logms:[581836]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57391):jpsuser:@logms:[1952976]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57392):jpsuser:@logms:[831288]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57393):jpsuser:@logms:[392980]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57394):jpsuser:@logms:[1808248]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57395):jpsuser:@logms:[1115492]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:::1(53827):OTP-DBMON$:@postgres:[1431392]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57396):jpsuser:@logms:[313220]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57397):jpsuser:@logms:[1848408]: FATAL: the database system is starting up
2017-02-10 10:06:46 KST:10.229.4.222(57398):jpsuser:@logms:[1971004]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57399):jpsuser:@logms:[133216]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57400):jpsuser:@logms:[1804992]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57401):jpsuser:@logms:[952720]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57402):jpsuser:@logms:[1952536]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57403):jpsuser:@logms:[1421912]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:::1(53828):jpsuser:@logms:[1190384]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57404):jpsuser:@logms:[1375484]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57405):jpsuser:@logms:[884540]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:::1(53829):jpsuser:@logms:[1355268]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:::1(53830):OTP-DBMON$:@postgres:[627692]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57406):jpsuser:@logms:[1948592]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57407):jpsuser:@logms:[816684]: FATAL: the database system is starting up
2017-02-10 10:06:47 KST:10.229.4.222(57408):jpsuser:@logms:[301204]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57409):jpsuser:@logms:[766604]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57410):jpsuser:@logms:[1802600]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57411):jpsuser:@logms:[744788]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57412):jpsuser:@logms:[1853840]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57413):jpsuser:@logms:[614280]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:::1(53831):jpsuser:@logms:[840052]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57414):jpsuser:@logms:[384964]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57415):jpsuser:@logms:[701812]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57416):jpsuser:@logms:[1420116]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:::1(53832):OTP-DBMON$:@postgres:[284112]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57417):jpsuser:@logms:[413572]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57418):jpsuser:@logms:[33932]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.222.7.143(65087):jpsuser:@logms:[1110624]: FATAL: the database system is starting up
2017-02-10 10:06:48 KST:10.229.4.222(57419):jpsuser:@logms:[816500]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65088):jpsuser:@logms:[508720]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57420):jpsuser:@logms:[1335540]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65089):jpsuser:@logms:[1977032]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57421):jpsuser:@logms:[1242956]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65090):jpsuser:@logms:[1586564]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57422):jpsuser:@logms:[1540116]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65091):jpsuser:@logms:[486512]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57423):jpsuser:@logms:[1189924]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65092):jpsuser:@logms:[1867876]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57424):jpsuser:@logms:[660860]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65093):jpsuser:@logms:[277144]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57425):jpsuser:@logms:[206776]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65094):jpsuser:@logms:[508540]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57426):jpsuser:@logms:[1125252]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65095):jpsuser:@logms:[1879448]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57427):jpsuser:@logms:[1678184]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65096):jpsuser:@logms:[1163796]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57428):jpsuser:@logms:[1362896]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:::1(53833):OTP-DBMON$:@postgres:[354784]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65097):jpsuser:@logms:[817620]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.229.4.222(57429):jpsuser:@logms:[1314848]: FATAL: the database system is starting up
2017-02-10 10:06:49 KST:10.222.7.143(65098):jpsuser:@logms:[478620]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57430):jpsuser:@logms:[1006264]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65099):jpsuser:@logms:[141364]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57431):jpsuser:@logms:[215608]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65100):jpsuser:@logms:[1156100]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57432):jpsuser:@logms:[1342584]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65101):jpsuser:@logms:[930600]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57433):jpsuser:@logms:[1914244]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65102):jpsuser:@logms:[26108]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57434):jpsuser:@logms:[1432044]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65103):jpsuser:@logms:[168056]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57435):jpsuser:@logms:[771840]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65104):jpsuser:@logms:[919520]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57436):jpsuser:@logms:[935168]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:::1(53836):jpsuser:@logms:[616992]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57437):jpsuser:@logms:[1066460]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65105):jpsuser:@logms:[556152]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57438):jpsuser:@logms:[444832]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65106):jpsuser:@logms:[1537064]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:::1(53837):jpsuser:@logms:[303920]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57439):jpsuser:@logms:[1074316]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65107):jpsuser:@logms:[1944276]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:::1(53838):OTP-DBMON$:@postgres:[205604]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.229.4.222(57440):jpsuser:@logms:[540760]: FATAL: the database system is starting up
2017-02-10 10:06:50 KST:10.222.7.143(65110):jpsuser:@logms:[659788]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57441):jpsuser:@logms:[1534552]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65111):jpsuser:@logms:[534700]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57442):jpsuser:@logms:[241132]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65112):jpsuser:@logms:[1026280]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57443):jpsuser:@logms:[1055760]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65113):jpsuser:@logms:[839276]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57444):jpsuser:@logms:[1245140]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65114):jpsuser:@logms:[1595784]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57445):jpsuser:@logms:[1162592]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65115):jpsuser:@logms:[1258788]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57446):jpsuser:@logms:[1030876]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65116):jpsuser:@logms:[31880]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:::1(53839):jpsuser:@logms:[935536]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57447):jpsuser:@logms:[906260]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65117):jpsuser:@logms:[427020]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:::1(53840):jpsuser:@logms:[255496]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57448):jpsuser:@logms:[1341904]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65118):jpsuser:@logms:[796384]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57449):jpsuser:@logms:[1588456]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65119):jpsuser:@logms:[467324]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57450):jpsuser:@logms:[158184]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:::1(53841):OTP-DBMON$:@postgres:[945836]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.222.7.143(65120):jpsuser:@logms:[74960]: FATAL: the database system is starting up
2017-02-10 10:06:51 KST:10.229.4.222(57451):jpsuser:@logms:[1437268]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65121):jpsuser:@logms:[241904]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57452):jpsuser:@logms:[938952]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65122):jpsuser:@logms:[1885772]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57453):jpsuser:@logms:[1036700]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65123):jpsuser:@logms:[1198004]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57454):jpsuser:@logms:[1169292]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65124):jpsuser:@logms:[1558648]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57455):jpsuser:@logms:[1766260]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65125):jpsuser:@logms:[1571664]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57456):jpsuser:@logms:[1984156]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65126):jpsuser:@logms:[1461960]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57457):jpsuser:@logms:[1669848]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65127):jpsuser:@logms:[1548636]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57458):jpsuser:@logms:[1690480]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65128):jpsuser:@logms:[309608]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57459):jpsuser:@logms:[1665896]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65130):jpsuser:@logms:[248156]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57460):jpsuser:@logms:[971320]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65131):jpsuser:@logms:[401948]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.229.4.222(57461):jpsuser:@logms:[343460]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:::1(53842):OTP-DBMON$:@postgres:[326108]: FATAL: the database system is starting up
2017-02-10 10:06:52 KST:10.222.7.143(65132):jpsuser:@logms:[100532]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57462):jpsuser:@logms:[1998956]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65133):jpsuser:@logms:[1422832]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57463):jpsuser:@logms:[1391656]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65134):jpsuser:@logms:[1663500]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57464):jpsuser:@logms:[1029976]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65135):jpsuser:@logms:[1197740]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57465):jpsuser:@logms:[1330208]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65136):jpsuser:@logms:[1505476]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57466):jpsuser:@logms:[1792288]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65137):jpsuser:@logms:[1021700]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57467):jpsuser:@logms:[390580]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65138):jpsuser:@logms:[1779876]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57468):jpsuser:@logms:[1367484]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65139):jpsuser:@logms:[380048]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:::1(53845):jpsuser:@logms:[1856192]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57469):jpsuser:@logms:[554824]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65140):jpsuser:@logms:[1137576]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57470):jpsuser:@logms:[888160]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65142):jpsuser:@logms:[1250188]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:::1(53847):jpsuser:@logms:[1492924]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57471):jpsuser:@logms:[483596]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.222.7.143(65143):jpsuser:@logms:[1531420]: FATAL: the database system is starting up
2017-02-10 10:06:53 KST:10.229.4.222(57472):jpsuser:@logms:[58628]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:::1(53849):OTP-DBMON$:@postgres:[39312]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65144):jpsuser:@logms:[885512]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57474):jpsuser:@logms:[338276]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65145):jpsuser:@logms:[1444976]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57475):jpsuser:@logms:[1961428]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65146):jpsuser:@logms:[1945984]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57476):jpsuser:@logms:[630024]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65147):jpsuser:@logms:[1197444]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57477):jpsuser:@logms:[841500]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65148):jpsuser:@logms:[904444]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57478):jpsuser:@logms:[235156]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65149):jpsuser:@logms:[1743396]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57479):jpsuser:@logms:[501196]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65150):jpsuser:@logms:[1805776]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57480):jpsuser:@logms:[185848]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:::1(53850):jpsuser:@logms:[1611020]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65151):jpsuser:@logms:[951128]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57481):jpsuser:@logms:[669204]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:::1(53854):jpsuser:@logms:[1182564]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65152):jpsuser:@logms:[830956]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:::@:[1728272]: LOG: record with zero length at 332/4C29AFC0
2017-02-10 10:06:54 KST:10.229.4.222(57482):jpsuser:@logms:[1834436]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:::@:[1728272]: LOG: redo done at 332/4C29AF90
2017-02-10 10:06:54 KST:::@:[1728272]: LOG: last completed transaction was at log time 2017-02-10 06:59:04.412+09
2017-02-10 10:06:54 KST:10.222.7.143(65153):jpsuser:@logms:[1638536]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.229.4.222(57483):jpsuser:@logms:[1300468]: FATAL: the database system is starting up
2017-02-10 10:06:54 KST:10.222.7.143(65154):jpsuser:@logms:[1290884]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57484):jpsuser:@logms:[1733776]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:::1(53855):OTP-DBMON$:@postgres:[499172]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65155):jpsuser:@logms:[1426608]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57485):jpsuser:@logms:[1956640]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65156):jpsuser:@logms:[1837640]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57486):jpsuser:@logms:[997844]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65157):jpsuser:@logms:[1852836]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57487):jpsuser:@logms:[1587120]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65158):jpsuser:@logms:[705144]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57488):jpsuser:@logms:[1056576]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65159):jpsuser:@logms:[381316]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57489):jpsuser:@logms:[834056]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65161):jpsuser:@logms:[1961008]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57490):jpsuser:@logms:[228808]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65162):jpsuser:@logms:[704052]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57491):jpsuser:@logms:[946040]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65163):jpsuser:@logms:[730136]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57492):jpsuser:@logms:[445528]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65164):jpsuser:@logms:[728412]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57493):jpsuser:@logms:[146112]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.222.7.143(65165):jpsuser:@logms:[434356]: FATAL: the database system is starting up
2017-02-10 10:06:55 KST:10.229.4.222(57494):jpsuser:@logms:[1860540]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65166):jpsuser:@logms:[1943364]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57495):jpsuser:@logms:[1668092]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:::1(53856):OTP-DBMON$:@postgres:[1233776]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65167):jpsuser:@logms:[1011856]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57496):jpsuser:@logms:[1103904]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65169):jpsuser:@logms:[1121144]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57497):jpsuser:@logms:[169320]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65170):jpsuser:@logms:[1589660]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57498):jpsuser:@logms:[1428992]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65171):jpsuser:@logms:[851432]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57499):jpsuser:@logms:[624604]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65172):jpsuser:@logms:[751972]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57500):jpsuser:@logms:[518372]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65174):jpsuser:@logms:[1477528]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57501):jpsuser:@logms:[550428]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65175):jpsuser:@logms:[1279016]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57502):jpsuser:@logms:[640880]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65176):jpsuser:@logms:[44132]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:::1(53857):jpsuser:@logms:[697972]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57503):jpsuser:@logms:[725976]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65177):jpsuser:@logms:[32468]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.229.4.222(57504):jpsuser:@logms:[1765284]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:::1(53860):jpsuser:@logms:[557616]: FATAL: the database system is starting up
2017-02-10 10:06:56 KST:10.222.7.143(65178):jpsuser:@logms:[1169260]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57505):jpsuser:@logms:[1022696]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65179):jpsuser:@logms:[1034116]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57506):jpsuser:@logms:[281288]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:::1(53861):OTP-DBMON$:@postgres:[193212]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65180):jpsuser:@logms:[464240]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57507):jpsuser:@logms:[1344728]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65181):jpsuser:@logms:[1414868]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57508):jpsuser:@logms:[1222292]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65182):jpsuser:@logms:[1939632]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57509):jpsuser:@logms:[642324]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65183):jpsuser:@logms:[291100]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57510):jpsuser:@logms:[1751500]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65184):jpsuser:@logms:[1078292]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57511):jpsuser:@logms:[1091804]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65185):jpsuser:@logms:[193064]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57512):jpsuser:@logms:[1280264]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65186):jpsuser:@logms:[1575660]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:::1(53862):jpsuser:@logms:[1440644]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57513):jpsuser:@logms:[1208664]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65187):jpsuser:@logms:[949632]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:::1(53864):jpsuser:@logms:[1876924]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57514):jpsuser:@logms:[1819580]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.222.7.143(65188):jpsuser:@logms:[87556]: FATAL: the database system is starting up
2017-02-10 10:06:57 KST:10.229.4.222(57515):jpsuser:@logms:[1728472]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65189):jpsuser:@logms:[878108]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57516):jpsuser:@logms:[860600]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65190):jpsuser:@logms:[497204]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57517):jpsuser:@logms:[566596]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:::1(53865):OTP-DBMON$:@postgres:[1603152]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65191):jpsuser:@logms:[1050932]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57518):jpsuser:@logms:[888640]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65192):jpsuser:@logms:[438796]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57519):jpsuser:@logms:[521844]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65193):jpsuser:@logms:[1375364]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57520):jpsuser:@logms:[1783132]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65194):jpsuser:@logms:[1855580]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57521):jpsuser:@logms:[1768096]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65195):jpsuser:@logms:[178724]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57522):jpsuser:@logms:[290652]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65196):jpsuser:@logms:[1722068]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57523):jpsuser:@logms:[1677984]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57524):jpsuser:@logms:[1181804]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65197):jpsuser:@logms:[1187536]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57525):jpsuser:@logms:[90600]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65198):jpsuser:@logms:[578920]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.229.4.222(57526):jpsuser:@logms:[1130668]: FATAL: the database system is starting up
2017-02-10 10:06:58 KST:10.222.7.143(65199):jpsuser:@logms:[1940512]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57527):jpsuser:@logms:[38880]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.222.7.143(65200):jpsuser:@logms:[44180]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57528):jpsuser:@logms:[943672]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.222.7.143(65201):jpsuser:@logms:[706340]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:::1(53866):OTP-DBMON$:@postgres:[190956]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57529):jpsuser:@logms:[279984]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.222.7.143(65202):jpsuser:@logms:[125524]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57530):jpsuser:@logms:[1382432]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.222.7.143(65203):jpsuser:@logms:[299136]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57531):jpsuser:@logms:[830724]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.222.7.143(65204):jpsuser:@logms:[388732]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57532):jpsuser:@logms:[1611928]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57533):jpsuser:@logms:[1722820]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57534):jpsuser:@logms:[971228]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57535):jpsuser:@logms:[1970048]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:::1(53867):jpsuser:@logms:[1450088]: FATAL: the database system is starting up
2017-02-10 10:06:59 KST:10.229.4.222(57536):jpsuser:@logms:[1648548]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57537):jpsuser:@logms:[475460]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:::1(53868):jpsuser:@logms:[74592]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57538):jpsuser:@logms:[753656]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57539):jpsuser:@logms:[245504]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57540):jpsuser:@logms:[988820]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:::1(53869):OTP-DBMON$:@postgres:[858612]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57541):jpsuser:@logms:[1596400]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57542):jpsuser:@logms:[1047728]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57543):jpsuser:@logms:[507152]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57544):jpsuser:@logms:[1116820]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57545):jpsuser:@logms:[76360]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:::1(53870):jpsuser:@logms:[1027904]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57546):jpsuser:@logms:[158208]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:::1(53871):jpsuser:@logms:[990880]: FATAL: the database system is starting up
2017-02-10 10:07:00 KST:10.229.4.222(57547):jpsuser:@logms:[271124]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57548):jpsuser:@logms:[716284]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57549):jpsuser:@logms:[1635128]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57550):jpsuser:@logms:[788856]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57551):jpsuser:@logms:[868424]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:::1(53873):OTP-DBMON$:@postgres:[41752]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57552):jpsuser:@logms:[1252884]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57553):jpsuser:@logms:[339212]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57554):jpsuser:@logms:[1144000]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57555):jpsuser:@logms:[1618016]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57556):jpsuser:@logms:[407776]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57557):jpsuser:@logms:[1092192]: FATAL: the database system is starting up
2017-02-10 10:07:01 KST:10.229.4.222(57558):jpsuser:@logms:[1513324]: FATAL: the database system is starting up
2017-02-10 10:07:02 KST:10.229.4.222(57559):jpsuser:@logms:[1341336]: FATAL: the database system is starting up
2017-02-10 10:07:02 KST:10.229.4.222(57560):jpsuser:@logms:[746916]: FATAL: the database system is starting up
2017-02-10 10:07:02 KST:10.229.4.222(57561):jpsuser:@logms:[935560]: FATAL: the database system is starting up
2017-02-10 10:07:02 KST:::@:[1096324]: LOG: database system is ready to accept connections
2017-02-10 10:07:02 KST:::@:[1564108]: LOG: autovacuum launcher started
2017-02-10 10:09:10 KST:10.229.4.207(49808):jpsuser:@logms:[779548]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:09:10 KST:10.229.4.207(49804):jpsuser:@logms:[562796]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:11:54 KST:10.229.4.207(49844):[unknown]:@[unknown]:[1148944]: LOG: incomplete startup packet
2017-02-10 10:50:07 KST:10.229.4.207(49803):jpsuser:@logms:[336120]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49976):jpsuser:@logms:[444528]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49961):jpsuser:@logms:[148288]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49963):jpsuser:@logms:[754944]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49980):jpsuser:@logms:[1688284]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49964):jpsuser:@logms:[563032]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49965):jpsuser:@logms:[929188]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49979):jpsuser:@logms:[1192136]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49981):jpsuser:@logms:[198140]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49977):jpsuser:@logms:[30088]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49825):jpsuser:@logms:[1957872]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49978):jpsuser:@logms:[1007736]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 10:50:07 KST:10.229.4.207(49962):jpsuser:@logms:[267948]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 11:02:16 KST:10.229.4.207(50294):jpsuser:@logms:[596904]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 11:02:16 KST:10.229.4.207(50295):jpsuser:@logms:[1437716]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 11:02:16 KST:10.229.4.207(50291):jpsuser:@logms:[1823876]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 11:02:16 KST:10.229.4.207(50178):jpsuser:@logms:[1619064]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it
2017-02-10 11:02:16 KST:10.229.4.207(50290):jpsuser:@logms:[199876]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it
2017-02-10 11:02:16 KST:10.229.4.207(50292):jpsuser:@logms:[1860364]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 11:02:16 KST:10.229.4.207(50293):jpsuser:@logms:[675820]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
2017-02-10 11:02:16 KST:10.229.4.207(50169):jpsuser:@logms:[1792512]: LOG: could not receive data from client: No connection could be made because the target machine actively refused it.
아래는 pg_hba.conf 와 postgresql.conf 내용입니다.
================================================================================================
# IPv4 local connections:
host all all 127.0.0.1/32 md5
host all all 192.168.0.0/0 md5
# IPv6 local connections:
host all all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#host replication postgres 127.0.0.1/32 md5
#host replication postgres ::1/128 md5
===============================================================================================================
# PostgreSQL configuration file
# -----------------------------
#
# This file consists of lines of the form:
#
# name = value
#
# (The "=" is optional.) Whitespace may be used. Comments are introduced with
# "#" anywhere on a line. The complete list of parameter names and allowed
# values can be found in the PostgreSQL documentation.
#
# The commented-out settings shown in this file represent the default values.
# Re-commenting a setting is NOT sufficient to revert it to the default value;
# you need to reload the server.
#
# This file is read on server startup and when the server receives a SIGHUP
# signal. If you edit the file on a running system, you have to SIGHUP the
# server for the changes to take effect, or use "pg_ctl reload". Some
# parameters, which are marked below, require a server shutdown and restart to
# take effect.
#
# Any parameter can also be given as a command-line option to the server, e.g.,
# "postgres -c log_connections=on". Some parameters can be changed at run time
# with the "SET" SQL command.
#
# Memory units: kB = kilobytes Time units: ms = milliseconds
# MB = megabytes s = seconds
# GB = gigabytes min = minutes
# h = hours
# d = days
#------------------------------------------------------------------------------
# FILE LOCATIONS
#------------------------------------------------------------------------------
# The default values of these variables are driven from the -D command-line
# option or PGDATA environment variable, represented here as ConfigDir.
#data_directory = 'ConfigDir' # use data in another directory
# (change requires restart)
#hba_file = 'ConfigDir/pg_hba.conf' # host-based authentication file
# (change requires restart)
#ident_file = 'ConfigDir/pg_ident.conf' # ident configuration file
# (change requires restart)
# If external_pid_file is not explicitly set, no extra PID file is written.
#external_pid_file = '' # write an extra PID file
# (change requires restart)
#------------------------------------------------------------------------------
# CONNECTIONS AND AUTHENTICATION
#------------------------------------------------------------------------------
# - Connection Settings -
listen_addresses = '*' # what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost'; use '*' for all
# (change requires restart)
port = 1610 # (change requires restart)
max_connections = 1000 # (change requires restart)
# Note: Increasing max_connections costs ~400 bytes of shared memory per
# connection slot, plus lock space (see max_locks_per_transaction).
#superuser_reserved_connections = 3 # (change requires restart)
#unix_socket_directory = '' # (change requires restart)
#unix_socket_group = '' # (change requires restart)
#unix_socket_permissions = 0777 # begin with 0 to use octal notation
# (change requires restart)
#bonjour = off # advertise server via Bonjour
# (change requires restart)
#bonjour_name = '' # defaults to the computer name
# (change requires restart)
# - Security and Authentication -
#authentication_timeout = 1min # 1s-600s
#ssl = off # (change requires restart)
#ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH' # allowed SSL ciphers
# (change requires restart)
#ssl_renegotiation_limit = 512MB # amount of data between renegotiations
#ssl_cert_file = 'server.crt' # (change requires restart)
#ssl_key_file = 'server.key' # (change requires restart)
#ssl_ca_file = '' # (change requires restart)
#ssl_crl_file = '' # (change requires restart)
#password_encryption = on
#db_user_namespace = off
# Kerberos and GSSAPI
#krb_server_keyfile = ''
#krb_srvname = 'postgres' # (Kerberos only)
#krb_caseins_users = off
# - TCP Keepalives -
# see "man 7 tcp" for details
#tcp_keepalives_idle = 0 # TCP_KEEPIDLE, in seconds;
# 0 selects the system default
#tcp_keepalives_interval = 0 # TCP_KEEPINTVL, in seconds;
# 0 selects the system default
#tcp_keepalives_count = 0 # TCP_KEEPCNT;
# 0 selects the system default
#------------------------------------------------------------------------------
# RESOURCE USAGE (except WAL)
#------------------------------------------------------------------------------
# - Memory -
shared_buffers = 450MB # min 128kB
# (change requires restart)
temp_buffers = 5MB # min 800kB
#max_prepared_transactions = 0 # zero disables the feature
# (change requires restart)
# Note: Increasing max_prepared_transactions costs ~600 bytes of shared memory
# per transaction slot, plus lock space (see max_locks_per_transaction).
# It is not advisable to set max_prepared_transactions nonzero unless you
# actively intend to use prepared transactions.
work_mem = 1MB # min 64kB
maintenance_work_mem = 32MB # min 1MB
#max_stack_depth = 2MB # min 100kB
# - Disk -
#temp_file_limit = -1 # limits per-session temp file space
# in kB, or -1 for no limit
# - Kernel Resource Usage -
#max_files_per_process = 1000 # min 25
# (change requires restart)
#shared_preload_libraries = 'pg_stat_statements' # (change requires restart)
# - Cost-Based Vacuum Delay -
#vacuum_cost_delay = 0ms # 0-100 milliseconds
#vacuum_cost_page_hit = 1 # 0-10000 credits
#vacuum_cost_page_miss = 10 # 0-10000 credits
#vacuum_cost_page_dirty = 20 # 0-10000 credits
#vacuum_cost_limit = 200 # 1-10000 credits
# - Background Writer -
#bgwriter_delay = 200ms # 10-10000ms between rounds
#bgwriter_lru_maxpages = 100 # 0-1000 max buffers written/round
#bgwriter_lru_multiplier = 2.0 # 0-10.0 multipler on buffers scanned/round
# - Asynchronous Behavior -
#effective_io_concurrency = 1 # 1-1000; 0 disables prefetching
#------------------------------------------------------------------------------
# WRITE AHEAD LOG
#------------------------------------------------------------------------------
# - Settings -
#wal_level = minimal # minimal, archive, or hot_standby
# (change requires restart)
#fsync = on # turns forced synchronization on or off
#synchronous_commit = on # synchronization level;
# off, local, remote_write, or on
#wal_sync_method = fsync # the default is the first option
# supported by the operating system:
# open_datasync
# fdatasync (default on Linux)
# fsync
# fsync_writethrough
# open_sync
#full_page_writes = on # recover from partial page writes
wal_buffers = 16MB # min 32kB, -1 sets based on shared_buffers
# (change requires restart)
#wal_writer_delay = 200ms # 1-10000 milliseconds
#commit_delay = 0 # range 0-100000, in microseconds
#commit_siblings = 5 # range 1-1000
# - Checkpoints -
checkpoint_segments = 10 # in logfile segments, min 1, 16MB each
#checkpoint_timeout = 5min # range 30s-1h
#checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0
#checkpoint_warning = 30s # 0 disables
# - Archiving -
#archive_mode = off # allows archiving to be done
# (change requires restart)
#archive_command = '' # command to use to archive a logfile segment
# placeholders: %p = path of file to archive
# %f = file name only
# e.g. 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f'
#archive_timeout = 0 # force a logfile segment switch after this
# number of seconds; 0 disables
#------------------------------------------------------------------------------
# REPLICATION
#------------------------------------------------------------------------------
# - Sending Server(s) -
# Set these on the master and on any standby that will send replication data.
#max_wal_senders = 0 # max number of walsender processes
# (change requires restart)
#wal_keep_segments = 0 # in logfile segments, 16MB each; 0 disables
#replication_timeout = 60s # in milliseconds; 0 disables
# - Master Server -
# These settings are ignored on a standby server.
#synchronous_standby_names = '' # standby servers that provide sync rep
# comma-separated list of application_name
# from standby(s); '*' = all
#vacuum_defer_cleanup_age = 0 # number of xacts by which cleanup is delayed
# - Standby Servers -
# These settings are ignored on a master server.
#hot_standby = off # "on" allows queries during recovery
# (change requires restart)
#max_standby_archive_delay = 30s # max delay before canceling queries
# when reading WAL from archive;
# -1 allows indefinite delay
#max_standby_streaming_delay = 30s # max delay before canceling queries
# when reading streaming WAL;
# -1 allows indefinite delay
#wal_receiver_status_interval = 10s # send replies at least this often
# 0 disables
#hot_standby_feedback = off # send info from standby to prevent
# query conflicts
#------------------------------------------------------------------------------
# QUERY TUNING
#------------------------------------------------------------------------------
# - Planner Method Configuration -
#enable_bitmapscan = on
#enable_hashagg = on
#enable_hashjoin = on
#enable_indexscan = on
#enable_indexonlyscan = on
#enable_material = on
#enable_mergejoin = on
#enable_nestloop = on
#enable_seqscan = on
#enable_sort = on
#enable_tidscan = on
# - Planner Cost Constants -
#seq_page_cost = 1.0 # measured on an arbitrary scale
random_page_cost = 2.0 # same scale as above
#cpu_tuple_cost = 0.01 # same scale as above
#cpu_index_tuple_cost = 0.005 # same scale as above
#cpu_operator_cost = 0.0025 # same scale as above
effective_cache_size = 1GB
# - Genetic Query Optimizer -
#geqo = on
#geqo_threshold = 12
#geqo_effort = 5 # range 1-10
#geqo_pool_size = 0 # selects default based on effort
#geqo_generations = 0 # selects default based on effort
#geqo_selection_bias = 2.0 # range 1.5-2.0
#geqo_seed = 0.0 # range 0.0-1.0
# - Other Planner Options -
default_statistics_target = 1000 # range 1-10000
#constraint_exclusion = partition # on, off, or partition
#cursor_tuple_fraction = 0.1 # range 0.0-1.0
#from_collapse_limit = 8
#join_collapse_limit = 8 # 1 disables collapsing of explicit
# JOIN clauses
#------------------------------------------------------------------------------
# ERROR REPORTING AND LOGGING
#------------------------------------------------------------------------------
# - Where to Log -
log_destination = 'stderr' # Valid values are combinations of
# stderr, csvlog, syslog, and eventlog,
# depending on platform. csvlog
# requires logging_collector to be on.
# This is used when logging to stderr:
logging_collector = on # Enable capturing of stderr and csvlog
# into log files. Required to be on for
# csvlogs.
# (change requires restart)
# These are only used if logging_collector is on:
#log_directory = 'pg_log' # directory where log files are written,
# can be absolute or relative to PGDATA
#log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,
# can include strftime() escapes
#log_file_mode = 0600 # creation mode for log files,
# begin with 0 to use octal notation
#log_truncate_on_rotation = off # If on, an existing log file with the
# same name as the new log file will be
# truncated rather than appended to.
# But such truncation only occurs on
# time-driven rotation, not on restarts
# or size-driven rotation. Default is
# off, meaning append to existing files
# in all cases.
#log_rotation_age = 1d # Automatic rotation of logfiles will
# happen after that time. 0 disables.
#log_rotation_size = 10MB # Automatic rotation of logfiles will
# happen after that much log output.
# 0 disables.
# These are relevant when logging to syslog:
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'
# This is only relevant when logging to eventlog (win32):
#event_source = 'PostgreSQL'
# - When to Log -
#client_min_messages = notice # values in order of decreasing detail:
# debug5
# debug4
# debug3
# debug2
# debug1
# log
# notice
# warning
# error
log_min_messages = log # values in order of decreasing detail:
# debug5
# debug4
# debug3
# debug2
# debug1
# info
# notice
# warning
# error
# log
# fatal
# panic
log_min_error_statement = log # values in order of decreasing detail:
# debug5
# debug4
# debug3
# debug2
# debug1
# info
# notice
# warning
# error
# log
# fatal
# panic (effectively off)
#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
# and their durations, > 0 logs only
# statements running at least this number
# of milliseconds
# - What to Log -
#debug_print_parse = off
#debug_print_rewritten = off
#debug_print_plan = off
#debug_pretty_print = on
#log_checkpoints = off
#log_connections = off
#log_disconnections = off
#log_duration = off
#log_error_verbosity = default # terse, default, or verbose messages
#log_hostname = off
log_line_prefix = '%t:%r:%u:@%d:[%p]: ' # special values:
# %a = application name
# %u = user name
# %d = database name
# %r = remote host and port
# %h = remote host
# %p = process ID
# %t = timestamp without milliseconds
# %m = timestamp with milliseconds
# %i = command tag
# %e = SQL state
# %c = session ID
# %l = session line number
# %s = session start timestamp
# %v = virtual transaction ID
# %x = transaction ID (0 if none)
# %q = stop here in non-session
# processes
# %% = '%'
# e.g. '<%u%%%d> '
#log_lock_waits = off # log lock waits >= deadlock_timeout
#log_statement = 'none' # none, ddl, mod, all
#log_temp_files = -1 # log temporary files equal or larger
# than the specified size in kilobytes;
# -1 disables, 0 logs all temp files
log_timezone = 'Asia/Seoul'
#------------------------------------------------------------------------------
# RUNTIME STATISTICS
#------------------------------------------------------------------------------
# - Query/Index Statistics Collector -
#track_activities = on
#track_counts = on
#track_io_timing = off
#track_functions = none # none, pl, all
track_activity_query_size = 4096 # (change requires restart)
#update_process_title = on
#stats_temp_directory = 'pg_stat_tmp'
# - Statistics Monitoring -
#log_parser_stats = off
#log_planner_stats = off
#log_executor_stats = off
#log_statement_stats = off
#------------------------------------------------------------------------------
# AUTOVACUUM PARAMETERS
#------------------------------------------------------------------------------
#autovacuum = on # Enable autovacuum subprocess? 'on'
# requires track_counts to also be on.
#log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and
# their durations, > 0 logs only
# actions running at least this number
# of milliseconds.
#autovacuum_max_workers = 3 # max number of autovacuum subprocesses
# (change requires restart)
#autovacuum_naptime = 1min # time between autovacuum runs
#autovacuum_vacuum_threshold = 50 # min number of row updates before
# vacuum
#autovacuum_analyze_threshold = 50 # min number of row updates before
# analyze
#autovacuum_vacuum_scale_factor = 0.2 # fraction of table size before vacuum
#autovacuum_analyze_scale_factor = 0.1 # fraction of table size before analyze
#autovacuum_freeze_max_age = 200000000 # maximum XID age before forced vacuum
# (change requires restart)
#autovacuum_vacuum_cost_delay = 20ms # default vacuum cost delay for
# autovacuum, in milliseconds;
# -1 means use vacuum_cost_delay
#autovacuum_vacuum_cost_limit = -1 # default vacuum cost limit for
# autovacuum, -1 means use
# vacuum_cost_limit
#------------------------------------------------------------------------------
# CLIENT CONNECTION DEFAULTS
#------------------------------------------------------------------------------
# - Statement Behavior -
#search_path = '"$user",public' # schema names
#default_tablespace = '' # a tablespace name, '' uses the default
#temp_tablespaces = '' # a list of tablespace names, '' uses
# only default tablespace
#check_function_bodies = on
#default_transaction_isolation = 'read committed'
#default_transaction_read_only = off
#default_transaction_deferrable = off
#session_replication_role = 'origin'
#statement_timeout = 0 # in milliseconds, 0 is disabled
#vacuum_freeze_min_age = 50000000
#vacuum_freeze_table_age = 150000000
#bytea_output = 'hex' # hex, escape
#xmlbinary = 'base64'
#xmloption = 'content'
# - Locale and Formatting -
datestyle = 'iso, ymd'
#intervalstyle = 'postgres'
timezone = 'ROK'
#timezone_abbreviations = 'Default' # Select the set of available time zone
# abbreviations. Currently, there are
# Default
# Australia
# India
# You can create your own file in
# share/timezonesets/.
#extra_float_digits = 0 # min -15, max 3
#client_encoding = sql_ascii # actually, defaults to database
# encoding
# These settings are initialized by initdb, but they can be changed.
lc_messages = 'Korean_Korea.949' # locale for system error message
# strings
lc_monetary = 'Korean_Korea.949' # locale for monetary formatting
lc_numeric = 'Korean_Korea.949' # locale for number formatting
lc_time = 'Korean_Korea.949' # locale for time formatting
# default configuration for text search
default_text_search_config = 'pg_catalog.simple'
# - Other Defaults -
#dynamic_library_path = '$libdir'
#local_preload_libraries = ''
#------------------------------------------------------------------------------
# LOCK MANAGEMENT
#------------------------------------------------------------------------------
deadlock_timeout = 5s
#max_locks_per_transaction = 64 # min 10
# (change requires restart)
# Note: Each lock table slot uses ~270 bytes of shared memory, and there are
# max_locks_per_transaction * (max_connections + max_prepared_transactions)
# lock table slots.
#max_pred_locks_per_transaction = 64 # min 10
# (change requires restart)
#------------------------------------------------------------------------------
# VERSION/PLATFORM COMPATIBILITY
#------------------------------------------------------------------------------
# - Previous PostgreSQL Versions -
#array_nulls = on
#backslash_quote = safe_encoding # on, off, or safe_encoding
#default_with_oids = off
#escape_string_warning = on
#lo_compat_privileges = off
#quote_all_identifiers = off
#sql_inheritance = on
#standard_conforming_strings = on
#synchronize_seqscans = on
# - Other Platforms and Clients -
#transform_null_equals = off
#------------------------------------------------------------------------------
# ERROR HANDLING
#------------------------------------------------------------------------------
#exit_on_error = off # terminate session on any error?
#restart_after_crash = on # reinitialize after backend crash?
#------------------------------------------------------------------------------
# CUSTOMIZED OPTIONS
#------------------------------------------------------------------------------
# Add settings for extensions here
#pg_stat_statements.max = 10000
제가 보기엔 conf설정은 문제가 없어보이는데 이유를 모르겠습니다. |