Re: Postgres 8.4.20 seqfault on RHEL 6.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Johansen <davejohansen(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgres 8.4.20 seqfault on RHEL 6.4
Date: 2015-02-13 02:35:26
Message-ID: 7740.1423794926@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Dave Johansen <davejohansen(at)gmail(dot)com> writes:
> Also, could this be caused by an issue or misuse of libpq/libpqxx in our
> application? If so, is there someway that we could turn on some sort of
> logging logging to see the queries or at least connections that we opening
> when or just before the crash happened?

A client should not be able to crash the server. (Ideally, anyway...)

As for logging, log_statements = all ought to help, though it might be
verbose.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Dave Johansen 2015-02-13 05:25:32 Re: Postgres 8.4.20 seqfault on RHEL 6.4
Previous Message Dave Johansen 2015-02-13 02:25:17 Re: Postgres 8.4.20 seqfault on RHEL 6.4