Re: Log, Logs and more Logs - Mailing list pgsql-sql

From Andrew Sullivan
Subject Re: Log, Logs and more Logs
Date
Msg-id 20070130213304.GA561@phlogiston.dyndns.org
Whole thread Raw
In response to Re: Log, Logs and more Logs  ("Ezequias Rodrigues da Rocha" <ezequias.rocha@gmail.com>)
Responses Re: Log, Logs and more Logs  ("Ezequias Rodrigues da Rocha" <ezequias.rocha@gmail.com>)
List pgsql-sql
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


pgsql-sql by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Differentiate Between Zero-Length String and NULLColumn Values
Next
From: "Ezequias Rodrigues da Rocha"
Date:
Subject: Re: Log, Logs and more Logs