Muhyiddin A.M Hayat wrote:
> Dear all,
>
> i'm unable to connect postgres server with error :
>
> C:\Program Files\PostgreSQL\8.2\bin>psql -U postgres siakad
> Password for user postgres:
> psql: server closed the connection unexpectedly
> This probably means the server terminated abnor
t; <[EMAIL PROTECTED]>
Cc:
Sent: Sunday, August 19, 2007 3:13 AM
Subject: Re: [GENERAL] server closed the connection unexpectedly
On 18/08/2007 19:30, Muhyiddin A.M Hayat wrote:
somebody help me please
You'll need to post a lot more information before anyone can help.
Is ther
On 18/08/2007 19:30, Muhyiddin A.M Hayat wrote:
somebody help me please
You'll need to post a lot more information before anyone can help.
Is there anything in the server log? - or the Windows event log?
Ray.
---
Raymond O'Donnell,
Dear all,
i'm unable to connect postgres server with error :
C:\Program Files\PostgreSQL\8.2\bin>psql -U postgres siakad
Password for user postgres:
psql: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the
Dear all,
i'm unable to connect postgres server with error :
C:\Program Files\PostgreSQL\8.2\bin>psql -U postgres siakad
Password for user postgres:
psql: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the
On Fri, 2006-10-06 at 11:20 -0400, Mark Greenbank wrote:
> Hi Richard,
>
> Thanks for the reply -- yeah, I know it's and old version but
> management has been reluctant to update a production database.
If there exists a patchlevel (the third component of the version) higher
than the one you're u
"Mark Greenbank" <[EMAIL PROTECTED]> writes:
> [ select count(*) from email_queue leads to ]
> LOG: server process (pid 26548) was terminated by signal 11
If this is repeatable then it probably indicates corrupt data on-disk
(which 7.3.2 is mostly lacking any defenses for). The trick is to find
Hi Doug,Are there any pointers as to how to fix corrupted data? Is seems like that might be the problem as I'm seeing a zero-length read in the log file (see my previous email).Thanks again,Mark
On 10/6/06, Douglas McNaught <[EMAIL PROTECTED]> wrote:
"Mark Greenbank" <[EMAIL PROTECTED]> writes:> 1)
I've enabled logging, having upgraded to 7.3.4 (since that was the simplest yum updated :) and I see the following messages:FATAL: unsupported frontend protocol
LOG: server process (pid 26548) was terminated by signal 11
LOG: terminating any other active server processesFATAL: The database syst
"Mark Greenbank" <[EMAIL PROTECTED]> writes:
> 1) I'm assuming that if I update 7.3.2 to 7.3.15 I can leave the data in place
> (that is, without doing a dump/restore) -- is this correct?
Yes--minor releases don't require dump/restore.
> 2) If I up upgrade to 8.x can just copy the data files or
Mark Greenbank wrote:
Hi,
I get this error when accessing the postgresl database -- any ideas? What
should I look at?
I can query all of the other tables in the database, just not the
email_queue table. Weird!
Thanks in advance,
Mark
# psql --version
psql (PostgreSQL) 7.3.2
contains support
Hi Richard,Thanks for the reply -- yeah, I know it's and old version but management has been reluctant to update a production database. As for the logs, I looked around an didn't see any. pg_ctl start is not using the -l option for logging and output is redirected to /dev/null :(
Anyway, now I have
Mark Greenbank wrote:
# psql --version
psql (PostgreSQL) 7.3.2
May I be the first to say "GODS ALIVE MAN! WHAT ARE YOU STILL DOING
RUNNING 7.3.2!". Even if you can't upgrade from 7.3, the latest release
is 7.3.15 - that's 13 sets of bug-fixes you're ignoring. There's a
passing chance one of
Hi,I get this error when accessing the postgresl database -- any ideas? What should I look at?
I can query all of the other tables in the database, just not the email_queue table. Weird!
Thanks in advance,
Mark# psql --versionpsql (PostgreSQL) 7.3.2
contains support for command-line editing
# psq
There was no crash that I know of.
# su postgres
$ cd /var/lib/pgsql/data
$ cat postmaster.pid
14877
/var/lib/pgsql/data
5432001393216
$ pg_ctl stop -D ./
waiting for postmaster to shut down..done
$ rm postmaster.pid
rm: imposível remover `postmaster.pid': Arquivo ou diretório não
encont
It seems that postgresql crashed recently, tried to restart
automatically, and has not succesfully restarted.
You will need to stop the postmaster daemon manually, probably delete
the postmaster.pid file, and restart the postmaster daemon.
Chances are that anyone trying to query the database is n
Hi all,
Errors running a psql batch that has worked for weeks without a
problem:
$ uname -a
Linux s1 2.6.6-1.435.2.3 #1 Thu Jul 1 08:25:29 EDT 2004 i686 athlon
i386 GNU/Linux
$ rpm -q postgresql
postgresql-7.4.2-1
$ psql KakaoStats
Bem-vindo ao psql 7.4.2, o terminal iterativo do PostgreSQL.
sel
Hi Mike:
Thanks for your answer, I'm unable to dump the table:
-bash-2.05b$ pg_dump -Fc -t afected_table database_name -f
./afected_table.dump
pg_dump: connection not open
pg_dump: lost synchronization with server, resetting connection
pg_dump: SQL command to dump the contents of table "afected_ta
Can you use pg_dump to backup the database and possibly then upgrade the
db? 7.2 is rather old. I recall reading similar postings in the
mailing this that recommend you upgrade to 7.2.4 or .6(?) if you must
stay on 7.2.
On Mon, 2004-07-05 at 17:48, ruben wrote:
> Hi:
>
> I'm getting this error
Hi:
I'm getting this error when accessing a table with certain WHERE condition:
"server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed."
I've read through
20 matches
Mail list logo
