jothiprasath216 <jothiprasath21@gmail.com> writes:
> Could you please let me know what are the other possibilities that could
> have caused this crash?
There was, absolutely positively, a log message emitted by that
elog/ereport call before it called abort(). If you didn't find it
then you're looking in the wrong place, or you have a broken
logging configuration.
Without that message nor any other information, it's impossible to
speculate further.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs