Re: postgresql-9.0 Windows service stops after database transaction

From: Thom Brown <thom(at)linux(dot)com>
To: adrian(dot)kitchingman(at)dse(dot)vic(dot)gov(dot)au
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: postgresql-9.0 Windows service stops after database transaction
Date: 2010-09-24 07:05:00
Message-ID: AANLkTi=0uRPHYdcLWZ1mbuGGNLn84=wqW97LNhaZt=Du@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 24 September 2010 05:39, <adrian(dot)kitchingman(at)dse(dot)vic(dot)gov(dot)au> wrote:
> Hi all
>
> I've have a strange problem with my Windows postgresql-9.0 service stopping
> after any transaction which manipulates tables in any database (Deleting
> records, Inserting records, bulk importing via \copy, etc). This problem
> occurs regardless whether I'm accessing the database server via pgAdmin III
> on a client machine or the server itself as well as through the command
> prompt. The end result it that I have to constantly restart the postgresql
> service after any transactions. Sometime there is a slight delay allowing a
> couple of transactions but the service is always eventually stopped.
>
> The problem appears to have started when I changed permissions on my machine
> to allow the user 'postgres' access to the C drive following the
> instructions in the last post of this thread:
> http://www.jitterbit.com/PhpBB/viewtopic.php?f=5&t=869
>
> The specs of postres environment are:
>
> Windows XP SP3
> PostgreSQL 9.0.0, compiled by Visual C++ build 1500, 32-bit
> pgAdmin III 1.12.0 (Sep17 2010, rev: REL-1_12_0)
> PostGIS 2.0SVN
>
> Hope someone can shed some light on this issue.

What appears in the logs?

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2010-09-24 14:17:43 Re: Memory usage - indexes
Previous Message adrian.kitchingman 2010-09-24 04:39:48 postgresql-9.0 Windows service stops after database transaction