Re: How can the error log be searched?

From: Adrian Klaver <aklaver(at)comcast(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: "Rob Richardson" <Rob(dot)Richardson(at)rad-con(dot)com>
Subject: Re: How can the error log be searched?
Date: 2008-12-29 21:27:03
Message-ID: 200812291327.03767.aklaver@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday 29 December 2008 11:28:13 am Rob Richardson wrote:
> Greetings!
>
> A customer reported an error generated by our database. However, many
> of our functions have errors in RAISE EXCEPTION statements, in which the
> % character was omitted. The error message the customer saw was
> complaining that there were too many arguments to a RAISE statement. We
> were able to find the function that was throwing the error by using
> PGAdmin, opening the Server Status window, going to the Log File tab,
> and finding approximately when the error occurred.
>
> But it would have been easier to find the problem if we could have
> searched the logs. There's no search function in the log file window.
> Also, there's no apparent way to export the file. Also, I can't even
> use copy and paste. So, how can I export the error messages into a
> searchable text file?
>
> Thanks very much!
>
> RobR

I don't use PgAdmin so I can't help you with that part. If you want to search
the file use ~/PGDATA/postgresql.conf to find the log directory and read the
file directly with the text editor of you choice.

--
Adrian Klaver
aklaver(at)comcast(dot)net

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christian Schröder 2008-12-29 23:13:13 Query planner and foreign key constraints
Previous Message Rob Richardson 2008-12-29 19:28:13 How can the error log be searched?