Re: psql: FATAL: the database system is in recovery mode

Hi

Thanks one again for your response.

>>You still haven't posted the offending query,
I am running on shell script that contains various select statment,
one of the example is as follows;
----------
SELECT PageIndex,
       (SUM(ConnectDoneTime - StartTime) * 100) / SUM(EndTime - StartTime)
AS "ConnectTimePct",
       (SUM(WriteCompleTime - ConnectDoneTime) * 100) / SUM(EndTime -
StartTime) AS "RequestSentTimePct",
       (SUM(FirstByteRcdTime - WriteCompleTime) * 100) / SUM(EndTime -
StartTime) AS "FirstByteTimePct",
       (SUM(EndTime - FirstByteRcdTime) * 100) / SUM(EndTime - StartTime) AS
"DownloadTimePct"
FROM UrlRecord_$1
WHERE EndTime <> 0
      AND ConnectDoneTime <> 0
      AND WriteCompleTime <> 0
      AND FirstByteRcdTime <> 0
GROUP By PageIndex
ORDER By PageIndex;

-----------

I want to tell you that its happening after sometime ie at random. time is
not fixed.

>>Is it a particular one, or does it crash at random?

its crash at random.


On 6/24/09, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
>
> Bhushan Verma wrote:
> >>> postmaster -D /var/lib/pgsql/data
> > I am using the same command as you said.
>
>
> I'm afraid I'm out of ideas on how to get the core dump then.
>
> You could also try attaching gdb to the backend process before it
> crashes, and get the backtrace from there. Something along the lines of:
>
>
> postmaster -D /var/lib/pgsql/data
>
> psql postgres ...
> ps ax | grep postgres # check the PID of the backend process psql is
> connected to.
> gdb
> gdb> attach <pid of backend>
> gdb> cont
> <run the query in psql that crashes>
> gdb> bt
>
>
> You still haven't posted the offending query, BTW. Is it a particular
> one, or does it crash at random?
>
>
> --
>
>   Heikki Linnakangas
>   EnterpriseDB   http://www.enterprisedb.com
>



--
With Regards,
Bhushan