From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dave Johansen <davejohansen@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres 8.4.20 seqfault on RHEL 6.4
Date: Thu, 12 Feb 2015 21:35:26 -0500
Message-ID: <7740.1423794926@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAcYxUdo_aMh=poLKP3yyeV0cVW=18YFWW-4sFwio+WdNuS3JQ@mail.gmail.com>
References: <CAAcYxUeduPhKXbDQ6ZTOhKGE+1A3cMrTQujSExC-tv4ac4ksUw@mail.gmail.com>
<16213.1423784028@sss.pgh.pa.us>
<CAAcYxUdo_aMh=poLKP3yyeV0cVW=18YFWW-4sFwio+WdNuS3JQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Dave Johansen <davejohansen@gmail.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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, davejohansen@gmail.com
Subject: Re: Postgres 8.4.20 seqfault on RHEL 6.4
In-Reply-To: <7740.1423794926@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox