database.sarang.net
UserID
Passwd
Database
DBMS
MySQL
ㆍPostgreSQL
Firebird
Oracle
Informix
Sybase
MS-SQL
DB2
Cache
CUBRID
LDAP
ALTIBASE
Tibero
DB 문서들
스터디
Community
공지사항
자유게시판
구인|구직
DSN 갤러리
도움주신분들
Admin
운영게시판
최근게시물
PostgreSQL Q&A 7482 게시물 읽기
No. 7482
테이블 컬럼을 변경했을시에 나는에러.
작성자
나윤성(앨버른)
작성일
2008-08-04 15:54
조회수
6,303

필요에 의해서 


 현재 기존에 사용하는 테이블 컬럼중


smallint형으로 저장하는 컬럼 타입을 integer 저장 타입으로 바꿧습니다.



이때 문제가 생긴게 insert는 잘되었으나


select시 어느 특정한 값에 대해서 읽어버리면 db가 죽어버리는 현상이 발생했습니다. 에러는


 3624 2008-08-04 14:03:53 KSTLOG:  server process (PID 3646) was terminated by signal 11

 3624 2008-08-04 14:03:53 KSTLOG:  terminating any other active server processes

3645 2008-08-04 14:03:53 KSTWARNING:  terminating connection because of crash of another server process

3645 2008-08-04 14:03:53 KSTDETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

 3645 2008-08-04 14:03:53 KSTHINT:  In a moment you should be able to reconnect to the database and repeat your command.

 3644 2008-08-04 14:03:53 KSTWARNING:  terminating connection because of crash of another server process

 3644 2008-08-04 14:03:53 KSTDETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

3644 2008-08-04 14:03:53 KSTHINT:  In a moment you should be able to reconnect to the database and repeat your command.

3643 2008-08-04 14:03:53 KSTWARNING:  terminating connection because of crash of another server process

3643 2008-08-04 14:03:53 KSTDETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

3643 2008-08-04 14:03:53 KSTHINT:  In a moment you should be able to reconnect to the database and repeat your command.

3642 2008-08-04 14:03:53 KSTWARNING:  terminating connection because of crash of another server process

3642 2008-08-04 14:03:53 KSTDETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

 3642 2008-08-04 14:03:53 KSTHINT:  In a moment you should be able to reconnect to the database and repeat your command.

 3624 2008-08-04 14:03:53 KSTLOG:  all server processes terminated; reinitializing

 3647 2008-08-04 14:03:53 KSTLOG:  database system was interrupted at 2008-08-04 14:02:14 KST

 3647 2008-08-04 14:03:53 KSTLOG:  checkpoint record is at B/E27C96C0

 3647 2008-08-04 14:03:53 KSTLOG:  redo record is at B/E27C96C0; undo record is at 0/0; shutdown TRUE

 3647 2008-08-04 14:03:53 KSTLOG:  next transaction ID: 0/36480288; next OID: 110634833

 3647 2008-08-04 14:03:53 KSTLOG:  next MultiXactId: 1; next MultiXactOffset: 0


 3647 2008-08-04 14:03:53 KSTLOG:  database system was not properly shut down; automatic recovery in progress

 3647 2008-08-04 14:03:53 KSTLOG:  record with zero length at B/E27C9708

 3647 2008-08-04 14:03:53 KSTLOG:  redo is not required

 3647 2008-08-04 14:03:53 KSTLOG:  database system is ready

 3650 2008-08-04 14:03:54 KSTLOG:  connection received: 



 3624 2008-08-04 14:03:59 KSTLOG:  server process (PID 3650) was terminated by signal 11

 3624 2008-08-04 14:03:59 KSTLOG:  terminating any other active server processes

 3624 2008-08-04 14:03:59 KSTLOG:  all server processes terminated; reinitializing

 3651 2008-08-04 14:03:59 KSTLOG:  database system was interrupted at 2008-08-04 14:03:53 KST

 3651 2008-08-04 14:03:59 KSTLOG:  checkpoint record is at B/E27C9708

 3651 2008-08-04 14:03:59 KSTLOG:  redo record is at B/E27C9708; undo record is at 0/0; shutdown TRUE

 3651 2008-08-04 14:03:59 KSTLOG:  next transaction ID: 0/36480288; next OID: 110634833

 3651 2008-08-04 14:03:59 KSTLOG:  next MultiXactId: 1; next MultiXactOffset: 0

 3651 2008-08-04 14:03:59 KSTLOG:  database system was not properly shut down; automatic recovery in progress

 3651 2008-08-04 14:03:59 KSTLOG:  record with zero length at B/E27C9750

 3651 2008-08-04 14:03:59 KSTLOG:  redo is not required

 3651 2008-08-04 14:03:59 KSTLOG:  database system is ready

 3653 2008-08-04 14:04:02 KSTLOG:  connection received: host= 3654 2008-08-04 14:04:05 KSTLOG:  connection received: host=


이런식으로 특정한 데이터를 select를 하면 db가 계속 죽는대 어떤 방법이 없을까요?



[Top]
No.
제목
작성자
작성일
조회
7485- [1]
아무개
2008-08-08
5735
7484카운트를 하려는데요 [1]
평평
2008-08-07
5721
7483레코드 ID로 복수테이블 생성 [6]
chunrima
2008-08-06
5884
7482테이블 컬럼을 변경했을시에 나는에러.
나윤성
2008-08-04
6303
7480증분 백업에 대해
레전드
2008-08-02
6717
7478인덱스 관련 질문(WHERE조건이 많을 경우)... [4]
오래된남자
2008-07-29
8321
7475count(*) 의 성능은? [4]
산하
2008-07-29
6993
Valid XHTML 1.0!
All about the DATABASE... Copyleft 1999-2024 DSN, All rights reserved.
작업시간: 0.016초, 이곳 서비스는
	PostgreSQL v16.2로 자료를 관리합니다