Re: Postgres service fails to start on Windows 2003 - Mailing list pgsql-general

From imaudi@comcast.net
Subject Re: Postgres service fails to start on Windows 2003
Date
Msg-id 1660267157.1393621235002671829.JavaMail.root@sz0074a.emeryville.ca.mail.comcast.net
Whole thread Raw
In response to Re: Postgres service fails to start on Windows 2003  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

Nope, the Postgres account is still in the "Users" group, I just changed the quota on that actual user account to have no limit.  Nothing else about the account has changed.

 

From what I can tell, the first time postgres attempts to start, it just hangs and the postgres.exe process lingers around in memory.  That's why I keep seeing these postmaster.pim files popup, and I can see several postgres.exe processes in memory as well.  I think the first time, NT just times out trying to start the service.  Then I go and try to start the service manually and get socket binding errors since the "hung" versions are still around.

 

I got this idea after running postgres.exe from the command line and it just hangs.  I seriously think some of my DB data is corrupted.  Most likely after creating a 1gig DB and running out of disk quota, something didn't get closed correctly or some file got corrupted and now the service won't start.  However, since I can't get into the server I can't try to nuke the DB.

 

Can I manually remove data files to erase a DB?  Basically I'm in a position where I need to keep my production DB and need to nuke my corrupted test DB.  Thanks!

 

Mike


----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Mike Christensen" <imaudi@comcast.net>
Cc: pgsql-general@postgresql.org
Sent: Wednesday, February 18, 2009 3:44:01 PM GMT -08:00 US/Canada Pacific
Subject: Re: [GENERAL] Postgres service fails to start on Windows 2003

Mike Christensen <imaudi@comcast.net> writes:
> I'm having problems getting the PostgreSQL service to start.  This
> started happening after I changed a disk quota to allow for larger
> database sizes, and no other configuration has changed.

You moved the Postgres account to some other group, right?

> 2009-02-18 14:02:51 PST LOG:  could not bind IPv4 socket: No error

I'm betting this is actually some kind of permissions issue (with
Windows not being very helpful about letting PG know that).  Is there
such a thing as "allowed to connect to the internet" in your account
settings?

                        regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Query palns and tug-of-war with enable_sort
Next
From: crackeur@comcast.net
Date:
Subject: [ANN]VTD-XML 2.5