On Tue, 2009-09-01 at 12:17 +0530, Bhushan Verma wrote:
>
> But my fedora 9 machine have as follows postgres version.
> rpm -qa|grep postgres
> postgresql-server-8.3.1-1.fc9.i386
Please note that you will need to follow this procedure before updating
PostgreSQL on Fedora 9:
https://fedoraproject
On Tue, Sep 1, 2009 at 8:47 AM, Bhushan Verma wrote:
> But my fedora 9 machine have as follows postgres version.
> rpm -qa|grep postgres
> postgresql-server-8.3.1-1.fc9.i386
> postgresql-devel-8.3.1-1.fc9.i386
> postgresql-python-8.3.1-1.fc9.i386
> postgresql-8.3.1-1.fc9.i386
> postgresql-libs-8.3.
Hi,
Sorry that was for my fedora 4 machine.
But my fedora 9 machine have as follows postgres version.
rpm -qa|grep postgres
postgresql-server-8.3.1-1.fc9.i386
postgresql-devel-8.3.1-1.fc9.i386
postgresql-python-8.3.1-1.fc9.i386
postgresql-8.3.1-1.fc9.i386
postgresql-libs-8.3.1-1.fc9.i386
I am ge
Bhushan Verma writes:
> - What version of PostgreSQL you are using?
> #rpm -qa|grep postgres
> postgresql-server-8.0.3-1
8.0.3 is four years obsolete. If you can still reproduce the crash
after updating to some recent 8.0.x version, it'd be worth looking
closer.
regards,
Hi,
Sorry for the insufficient information.
As follows is the infomrations:
- What version of PostgreSQL you are using?
#rpm -qa|grep postgres
postgresql-server-8.0.3-1
postgresql-libs-8.0.3-1
postgresql-odbc-08.00.0100-1
postgresql-jdbc-8.0.3-1
postgresql-docs-8.0.3-1
postgresql-tcl-8.0.3-1
postg
Bhushan Verma wrote:
> Hi All,
>
> I am trying to run as follows queries
> --
> SELECT PageIndex,
>(SUM(ConnectDoneTime - StartTime) * 100) / SUM(EndTime - StartTime)
> AS "ConnectTimePct",
>(SUM(WriteCompleTime - ConnectDoneTime) * 100) / SUM(EndTime -
> StartTime) AS "R
Hi All,
I am trying to run as follows queries
--
SELECT PageIndex,
(SUM(ConnectDoneTime - StartTime) * 100) / SUM(EndTime - StartTime)
AS "ConnectTimePct",
(SUM(WriteCompleTime - ConnectDoneTime) * 100) / SUM(EndTime -
StartTime) AS "RequestSentTimePct",
(SUM(FirstBy
Bhushan Verma wrote:
>>> Is it a particular one, or does it crash at random?
>
> its crash at random.
Random segfaults easily by application bugs ( memory corruption,
accessing uninitialized memory and dereferencing pointers there, etc )
or hardware issues like bad CPU/CPU cache/memory, overheat
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 "
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 line
Bhushan Verma wrote:
>> The core file is generated in the data directory. I believe the default
>> location on Fedora is /var/lib/pgsql/dat
>
> Yes I also think the same.
> But there is no core file in /var/lib/pgsql/dat on my system.
> I am trying to find out why this is not generating core while
>The core file is generated in the data directory. I believe the default
>location on Fedora is /var/lib/pgsql/dat
Yes I also think the same.
But there is no core file in /var/lib/pgsql/dat on my system.
I am trying to find out why this is not generating core while log message
"LOG: server proces
Bhushan Verma wrote:
> I have searched for the core file for this pid.
> Is there any spcefic path for the postgres executable?
>
> I have already checked for ulimit -c unlimited etc.
> On my system core file for some other application are generating properly.
The core file is generated in the da
Hi,
Thanks for your response.
I am not able to find out the core file.
but in log file its giving the message like:
LOG: server process (PID 29225) was terminated by signal 11: Segmentation
fault
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitia
Thanks for your response.
As follows is log details
ERROR: table "transactionrecord_5917" does not exist
STATEMENT: drop table TransactionRecord_5917;
ERROR: table "pagerecord_5917" does not exist
STATEMENT: drop table PageRecord_5917;
ERROR: table "urlrecord_5917" does not exist
STATEMENT:
Bhushan Verma wrote:
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> connection to server was lost
Look in the PostgreSQL server logs for more information. It's probably
in /var/log/postgresql or someth
Bhushan Verma wrote:
> I am doing some database related queries and this is working fine at fedora
> core 4.
> But the same database queries giving the FATAL error on fedora 9.
>
> If I restarts the database on fedora core 9 then this is perfectlry working
> without giving any error.
>
> My postg
Hi All,
I am doing some database related queries and this is working fine at fedora
core 4.
But the same database queries giving the FATAL error on fedora 9.
If I restarts the database on fedora core 9 then this is perfectlry working
without giving any error.
My postgres version is
On Fedora co
18 matches
Mail list logo
