Re: [HACKERS] Postgres abort found in 9.3.11

2016-11-22 Thread K S, Sandhya (Nokia - IN/Bangalore)
] Postgres abort found in 9.3.11 "K S, Sandhya (Nokia - IN/Bangalore)" writes: > As suggested by you, we upgraded the postgres to version 9.3.14. Also we > removed all the patches we had applied before. But the issue is still > observed in the latest version as well. Can you m

Re: [HACKERS] Postgres abort found in 9.3.11

2016-11-21 Thread Tom Lane
"K S, Sandhya (Nokia - IN/Bangalore)" writes: > As suggested by you, we upgraded the postgres to version 9.3.14. Also we > removed all the patches we had applied before. But the issue is still > observed in the latest version as well. Can you make a test case for other people to try?

Re: [HACKERS] Postgres abort found in 9.3.11

2016-11-21 Thread K S, Sandhya (Nokia - IN/Bangalore)
] Sent: Friday, September 16, 2016 1:29 AM To: K S, Sandhya (Nokia - IN/Bangalore) Cc: pgsql-hackers@postgresql.org; Itnal, Prakash (Nokia - IN/Bangalore) Subject: Re: [HACKERS] Postgres abort found in 9.3.11 "K S, Sandhya (Nokia - IN/Bangalore)" writes: > We tried to replicate

Re: [HACKERS] Postgres abort found in 9.3.11

2016-09-15 Thread Tom Lane
"K S, Sandhya (Nokia - IN/Bangalore)" writes: > We tried to replicate the scenario without our patch(exiting postmaster) and > still we were able to see the issue. > Same error was seen this time as well. > node-0 postgres[8243]: [1-2] HINT: Is another postmaster already running on > port 5433

Re: [HACKERS] Postgres abort found in 9.3.11

2016-09-15 Thread K S, Sandhya (Nokia - IN/Bangalore)
!!! Sandhya -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Tuesday, September 06, 2016 5:04 PM To: K S, Sandhya (Nokia - IN/Bangalore) Cc: pgsql-hackers@postgresql.org; Itnal, Prakash (Nokia - IN/Bangalore) Subject: Re: [HACKERS] Postgres abort found in 9.3.11 "K S, Sa

Re: [HACKERS] Postgres abort found in 9.3.11

2016-09-06 Thread K S, Sandhya (Nokia - IN/Bangalore)
; Thanks in advance!!! Sandhya -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Thursday, September 01, 2016 7:19 PM To: K S, Sandhya (Nokia - IN/Bangalore) Cc: pgsql-hackers@postgresql.org; Itnal, Prakash (Nokia - IN/Bangalore) Subject: Re: [HACKERS] Postgres abort

Re: [HACKERS] Postgres abort found in 9.3.11

2016-09-06 Thread Tom Lane
"K S, Sandhya (Nokia - IN/Bangalore)" writes: > I was able to find a patch file where there is a call to ExitPostmaster() in > postmaster.c . > @@ -3081,6 +3081,11 @@ > shmem_exit(1); > reset_shared(PostPortNumber); > + /* recovery termination */ > + ereport(FATAL,

Re: [HACKERS] Postgres abort found in 9.3.11

2016-09-02 Thread K S, Sandhya (Nokia - IN/Bangalore)
; Itnal, Prakash (Nokia - IN/Bangalore) Subject: Re: [HACKERS] Postgres abort found in 9.3.11 "K S, Sandhya (Nokia - IN/Bangalore)" writes: > During the server restart, we are getting postgres crash with sigabrt. No > other operation being performed. > Attached the backtrace. W

Re: [HACKERS] Postgres abort found in 9.3.11

2016-09-01 Thread Tom Lane
"K S, Sandhya (Nokia - IN/Bangalore)" writes: > Our setup is a hot-standby architecture. This crash is occurring only on > stand-by node. Postgres continues to run without any issues on active node. > Postmaster is waiting for a start and is throwing this message. > Aug 22 11:44:21.462555 info n

Re: [HACKERS] Postgres abort found in 9.3.11

2016-08-30 Thread Tom Lane
"K S, Sandhya (Nokia - IN/Bangalore)" writes: > During the server restart, we are getting postgres crash with sigabrt. No > other operation being performed. > Attached the backtrace. What shows up in the postmaster log? > The occurrence is occasional. The issue is seen once in 30~50 times. Doe

[HACKERS] Postgres abort found in 9.3.11

2016-08-30 Thread K S, Sandhya (Nokia - IN/Bangalore)
Hello, During the server restart, we are getting postgres crash with sigabrt. No other operation being performed. Attached the backtrace. The occurrence is occasional. The issue is seen once in 30~50 times. Recently we had performed postgres upgrade from 9.3.9 to 9.3.11. The issue is not seen