Thread: Problem in starting PGSQL8.1 service.

I modified one of the .CONF files located in the Postgresql\Data Folder. I
just changed the amout of shared_Buffer from 1000 to 100 and Max_Connections
from 100 to 2.

But after that the PGSQL service stopped working. It stopped listening to
the local host. I have installed PostgreSQL on my desktop stand-alone
machine (as a service).

I changed the .CONF files to their default values, but still it stopped
working. Later I had to re-install it to get things work properly.

Please let me know why it happened and how to get rid of this problem.
--
View this message in context: http://www.nabble.com/Problem-in-starting-PGSQL8.1-service.-tf2052505.html#a5654742
Sent from the PostgreSQL - admin forum at Nabble.com.

2006. August 04. Friday 19.47 dátummal RPK ezt írta:
> I modified one of the .CONF files located in the Postgresql\Data
> Folder. I just changed the amout of shared_Buffer from 1000 to 100
> and Max_Connections from 100 to 2.
>
> But after that the PGSQL service stopped working. It stopped
> listening to the local host. I have installed PostgreSQL on my
> desktop stand-alone machine (as a service).
>
> I changed the .CONF files to their default values, but still it
> stopped working. Later I had to re-install it to get things work
> properly.
>
> Please let me know why it happened and how to get rid of this
> problem.

What do you see, then you run the "net start <service name>" command 
in your shell, and what is in the postgresql.log file?

bye,
kjt


McAfee SCM 4.1 által ellenőrizve!

> I modified one of the .CONF files located in the Postgresql\Data
> Folder. I just changed the amout of shared_Buffer from 1000 to 100
> and Max_Connections from 100 to 2.
>
> But after that the PGSQL service stopped working. It stopped
> listening to the local host. I have installed PostgreSQL on my
> desktop stand-alone machine (as a service).
>
> I changed the .CONF files to their default values, but still it
> stopped working. Later I had to re-install it to get things work
> properly.
>
> Please let me know why it happened and how to get rid of this
> problem.

You need to check your logfiles - both the ones in pg_log, and the
application eventlog. They should contain a hint about what's wrong.

//Magnus