Hi
I have been experimenting with Postgresql on windows since version 8.3.
However I never read much documentation.
Previously I was always using Windows XP Prof. with older versions of
Kaspersky Internet Security.
Recently I bought Windows 7 Prof. 32 bit and also the 2010 version of
Kaspersky.
I
Hi
Last night i mailed a message about me not being able to install Postgresql
8.4.3 successfully on windows 7 professional.
I have since temporary quitted my antivirus and firewall programs and I
could install successfull.
In the installation it askes you for a password which it uses for for the
On 6 Apr 2010, at 21:00, Heine Ferreira wrote:
Hi
Last night i mailed a message about me not being able to install Postgresql
8.4.3 successfully on windows 7 professional.
I have since temporary quitted my antivirus and firewall programs and I could
install successfull.
In the
Hi
My copy of PostgreSQL version 8.3 has decided not to receive a connection after
an idle time measured in hours.
It acceptes the connection one I stop the server and then restart. At this
point, it always asks for the password.
Here is the log of the event -
FATAL: could not reattach to
Bob Pawley wrote:
Hi
My copy of PostgreSQL version 8.3 has decided not to receive a
connection after an idle time measured in hours.
Odd.
It acceptes the connection one I stop the server and then restart. At
this point, it always asks for the password.
Here is the log of the event -
, 2009 10:24 AM
Subject: Re: [GENERAL] Can't connect
Bob Pawley wrote:
Hi
My copy of PostgreSQL version 8.3 has decided not to receive a
connection after an idle time measured in hours.
Odd.
It acceptes the connection one I stop the server and then restart. At
this point, it always asks
Bob Pawley wrote:
FATAL: could not reattach to shared memory (key=1804, addr=0170): 487
2009-10-29 00:19:20 PDT WARNING: worker took too long to start; cancelled
Is there some way of ensuring that the server always accepts a connection?
This is a known bug, supposedly fixed in 8.3.8.
Bob Pawley wrote:
I am on Windows and am running an anti virus program. But I was running
the same programs on Windows before without this problem.
Well, as long as you're happy you've ruled out your anti-virus, and
you're running 8.3.8 then you'll want to monitor it and next time it
happens
Thanks for your help with pg_resetxlog. It recovered all of our databases,
and it looks like we got lucky in that no updates were lost.
We are deciding on the goals for our next release, and one of the issues on
the table is an upgrade to postgres 8. Can you comment on the improvements
in
On 9/25/07, Morris Goldstein [EMAIL PROTECTED] wrote:
Thanks for your help with pg_resetxlog. It recovered all of our databases,
and it looks like we got lucky in that no updates were lost.
We are deciding on the goals for our next release, and one of the issues on
the table is an upgrade to
On 9/25/07, Scott Marlowe [EMAIL PROTECTED] wrote:
But since it hit all of your machines, and at about the same time, I
tend to think that someone did something to these machines that caused
this issue, and it's not a 7.4.x problem.
I'm sure it is pilot error, and we're still trying to
Morris Goldstein [EMAIL PROTECTED] writes:
We've recovered. There is root cause analysis going on. The question is
whether I can use an argument about 8.0 vs. 7.4 reliability from this fiasco
to help us get to 8.0.
8.0 actually is more reliable than 7.4, I assume.
I don't know that I'd make
On 9/25/07, Morris Goldstein [EMAIL PROTECTED] wrote:
On 9/25/07, Scott Marlowe [EMAIL PROTECTED] wrote:
But since it hit all of your machines, and at about the same time, I
tend to think that someone did something to these machines that caused
this issue, and it's not a 7.4.x problem.
We have a cluster with four nodes, each running a postgres 7.4.8
database. Due to a large amount of pilot error and possibly hardware
problems (still trying to get to the bottom of it all), two of the
databases won't start, and I can't login to two others, with any
registered user.
Two of the
Morris Goldstein [EMAIL PROTECTED] writes:
Two of the nodes have logs that look like this:
2007-09-22 07:06:05 [3060] LOG: could not open file
/var/lib/pgsql/data/pg_xlog/ (log file 0, segment
0): No such file or directory
2007-09-22 07:06:05 [3060] LOG: invalid primary
On 9/22/07, Tom Lane [EMAIL PROTECTED] wrote:
Morris Goldstein [EMAIL PROTECTED] writes:
Two of the nodes have logs that look like this:
2007-09-22 07:06:05 [3060] LOG: could not open file
/var/lib/pgsql/data/pg_xlog/ (log file 0, segment
0): No such file or directory
Sorry to reply to myself but here's a bit more info. That strace shows
a crash. The node that was denying logins is now complaining about
checkpoint file 000...000. It appears to be the case that a few
attempts to start converts a db that rejects logins to one that
crashes on startup. (When I
On 9/22/07, Tom Lane [EMAIL PROTECTED] wrote:
Morris Goldstein [EMAIL PROTECTED] writes:
...
2007-09-22 07:06:05 [3060] LOG: could not open file
/var/lib/pgsql/data/pg_xlog/ (log file 0, segment 0): No
such file or directory
...
...
You might be able to recover, at
Morris Goldstein [EMAIL PROTECTED] writes:
I looked at the pg_resetxlog documentation and have a question. Here
is output from pg_resetxlog -n:
[ snipped to just the non-constant numbers ]
Current log file ID: 0
Next log file segment:1
Latest checkpoint's
Hello,
I have a problem with postgresql 7.4 installed on Linux Ubuntu 5.04
(hoary).
I made an 'alter' command for my db users :
eg: alter user postgres with password 'postgres';
ALTER USER
but I can't connect to postgresql using :
tobini% psql -d template1 -U postgres -W
password: postgres
ctobini wrote:
Hello,
I have a problem with postgresql 7.4 installed on Linux Ubuntu 5.04
(hoary).
I made an 'alter' command for my db users :
eg: alter user postgres with password 'postgres';
ALTER USER
but I can't connect to postgresql using :
tobini% psql -d template1 -U
In article [EMAIL PROTECTED],
ctobini [EMAIL PROTECTED] wrote:
tobini% psql -d template1 -U postgres -W
password: postgres
psql: FATAL: IDENT authentication failed for user postgres
Do you have an idea about this problem ?
Use the su command to become user postgres and then run the
psql
After several years away from Postgres, I'm back to using it for a small
project.
I installed 7.4.8 on a FreeBSD 5.4-STABLE machine. Then I init'd the db and
added myself as a user, then created a ned db for the prohect. I can
connect fine with psql.
Then I built pgaccess, and p5-DBD-Pg-13 from
stan [EMAIL PROTECTED] writes:
After several years away from Postgres, I'm back to using it for a small
project.
I installed 7.4.8 on a FreeBSD 5.4-STABLE machine. Then I init'd the db and
added myself as a user, then created a ned db for the prohect. I can
connect fine with psql.
Then I
Chris Guo wrote:
I just installed postgresql 0.8.3 on the fedora core linux 3, I also
Version 8.0.3 I hope, 0.8.3 would be *very* old.
installed pgadmin 1.0.2 in my computer. But I am having trouble connecting
postgresql by using pgadmin, it shows me the error message An error
occurred:
Dear all,
I just installed postgresql 0.8.3 on the fedora core linux 3,
I also installed pgadmin 1.0.2 in my computer. But I am having trouble
connecting postgresql by using pgadmin, it shows me the error message An
error occurred: Error connecting to the server: could connect to
Hi again,
I still can't connect. I need someone to tell me what
I can try to discover what the problem is.
Again, here's the problem:
pgSQL 8.0.3 install on WinXP SP1.
The install works fine. The DB starts and works until
we restart the computer. When the machine reboots, we
can't connect to
Another question on the same matter:
Do I need XP SP2 for pgSQL 8.0.3 to work correctly? I have
all the security patches, but not SP2.
No, it shold work fine with both RTM and SP1.
(That said, I'd definitly recommend SP2, but that is as a general matter
not as a postgresql requirement)
Another question on the same matter:
Do I need XP SP2 for pgSQL 8.0.3 to work correctly? I
have all the security patches, but not SP2.
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Hi,
We've been having trouble with a pgSQL 8.0.3 install
on a WXP machine. Install goes fine, DB works until we
restart the machine, then we can't connect. First time
we thought something was corrupted because we had a
power outage, we uninstalled/reinstalled and it was
fine until, again, we
Audrey Bergeron-Morin wrote:
We've been having trouble with a pgSQL 8.0.3 install
on a WXP machine. Install goes fine, DB works until we
restart the machine, then we can't connect. First time
we thought something was corrupted because we had a
power outage, we uninstalled/reinstalled and it was
--- Matthew T. O'Connor matthew@zeut.net wrote:
Audrey Bergeron-Morin wrote:
We've been having trouble with a pgSQL 8.0.3
install
on a WXP machine. Install goes fine, DB works until
we
restart the machine, then we can't connect. First
time
we thought something was corrupted because we
Anony Mous [EMAIL PROTECTED] writes:
A few days ago there was a fellow that had trouble connecting remotely to
the 8.0 beta win port. I had the same problem, but have since found the
solution. In postgresql.conf file, ensure the line listen_addresses is
set to '*', ie,
listen_addresses =
Anony Mous [EMAIL PROTECTED] writes:
If so, why not set the listen_addresses to '*' right away?
Security. It was difficult enough to get people to accept the current
liberalized default --- I don't think they'll go for defaulting to -i,
which is essentially what you're asking for. It's seen as
On Wed, 2004-09-01 at 16:12, Doug McNaught wrote:
Anony Mous [EMAIL PROTECTED] writes:
A few days ago there was a fellow that had trouble connecting remotely to
the 8.0 beta win port. I had the same problem, but have since found the
solution. In postgresql.conf file, ensure the line
.
Thanks!
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: September 1, 2004 5:19 PM
To: Anony Mous
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] Can't connect to Windows port + other
Anony Mous [EMAIL PROTECTED] writes:
If so, why not set the listen_addresses
Anony Mous wrote:
Great, I found the part of the docs referring to this (ch 27.11) however, it
refers to creating this file in the user's home directory. It seems this
part of the documentation is assuming I'm using *nix. In Windows, where
should this file be located? Also, .pgpass is an
A software package i want to use requires postgresql version 6.2.1
Therefor i compiled and installed it, everything works fine. I can
connect to the server via psql in xterm.
But the software claims, that there is no postgre server running.
My hd_dba.conf has the correct settings:
host
Jeff wrote:
It is still strange though that I get different behavior
from the exact same source when built on two different
computers. I installed 7.0.2 on my laptop and I get an
interactive prompt "". On my linux box I installed 7.0.2
and I get a "#" as the last character in the psql
Thanks,
It is still strange though that I get different behavior
from the exact same source when built on two different
computers. I installed 7.0.2 on my laptop and I get an
interactive prompt "". On my linux box I installed 7.0.2
and I get a "#" as the last character in the psql prompt.
The
I was just about to give postgres 7.0.2 a try on my development machine,
but after installing it, I find that I can't connect to my 6.5.2
production servers. The following error message is reported by both psql
and pgaccess, upon trying to connect:
ERROR: MultiByte strings (MB) must be enabled
I was just about to give postgres 7.0.2 a try on my development machine,
but after installing it, I find that I can't connect to my 6.5.2
production servers. The following error message is reported by both psql
and pgaccess, upon trying to connect:
ERROR: MultiByte strings (MB) must be
42 matches
Mail list logo
