From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Log, Logs and more Logs
Date: Tue, 30 Jan 2007 16:33:04 -0500
Message-ID: <20070130213304.GA561@phlogiston.dyndns.org> (raw)
In-Reply-To: <55c095e90701301041u68c5acc7i99517994724aa6d4@mail.gmail.com>
References: <55c095e90701300901y41197404q4c26032ff0a28e22@mail.gmail.com>
<20070130172651.GD32170@phlogiston.dyndns.org>
<55c095e90701301041u68c5acc7i99517994724aa6d4@mail.gmail.com>
On Tue, Jan 30, 2007 at 04:41:13PM -0200, Ezequias Rodrigues da Rocha wrote:
> So you are tell me that it is impossible to retrieve it ok ?
No.
> Just by changing this values (what I did now) it is possible to get
> the error messages and their statements OK?.
Yes, but you need to signal the postmaster to reload its config file.
Either kill -SIGHUP or restart the postmaster. After that, you
should see the statement that caused your error. Note that if the
UPDATE itself doesn't cause the error, but say a later COMMIT (you
can get this in serializable mode easily), you'll see the COMMIT as
the thing that caused the error.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
Unfortunately reformatting the Internet is a little more painful
than reformatting your hard drive when it gets out of whack.
--Scott Morris
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-sql@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Log, Logs and more Logs
In-Reply-To: <20070130213304.GA561@phlogiston.dyndns.org>
* 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