From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Log, Logs and more Logs |
Date: | 2007-01-30 21:33:04 |
Message-ID: | 20070130213304.GA561@phlogiston.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support 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(at)crankycanuck(dot)ca
Unfortunately reformatting the Internet is a little more painful
than reformatting your hard drive when it gets out of whack.
--Scott Morris
From | Date | Subject | |
---|---|---|---|
Next Message | Ezequias Rodrigues da Rocha | 2007-01-31 11:35:03 | Re: Log, Logs and more Logs |
Previous Message | Ezequias Rodrigues da Rocha | 2007-01-30 18:41:13 | Re: Log, Logs and more Logs |
From | Date | Subject | |
---|---|---|---|
Next Message | Ezequias Rodrigues da Rocha | 2007-01-31 11:35:03 | Re: Log, Logs and more Logs |
Previous Message | Hiltibidal, Robert | 2007-01-30 20:42:11 | Index ANDing & Index ORing |