Re: [Gnumed-devel] gnumed upgrade failure.

[Busser, Jim]

On 2013-11-25, at 11:11 AM, Karsten Hilbert <address@hidden> wrote:

> On Mon, Nov 25, 2013 at 06:24:05PM +0000, Jim Busser wrote:
> 
>> Vaibhav, if you did not in the
>> meantime receive other
>> suggestions, you could try rebooting your machine before the
>> next time you attempt to bootstrap. That
>> should close the persisting connections that you were unaware
>> or unable to close and which gave rise to [Error 32].
> 
> It's worth a try but I'm not convinced that
> that's due to other clients let alone connections
> to the database.

You may be right, however I could not locate in my archive of email 
(gnumed-devel and gnumed-bugs) any previous instance of

        [Error 32]

and so it does not seem it is any normal part of what few windows logs have 
previously been posted.

I do still suspect there *could* be value, before Vaibhav would run the 
bootstrapper, to try the following adjusted for Windows (at bottom) to check 
what if anything else is connected to postgres and report back:

> # be sure no-one else is connected or logged-in (result should be 0, not more)
> psql -U postgres -c 'SELECT COUNT(*)-1 FROM pg_stat_activity;'
> 
> # more detail on the above:
> psql -U postgres -c 'SELECT datname, usename, query FROM pg_stat_activity;'

# on Windows:

C:\WINDOWS\Temp>c:\Programme\PostgreSQL\9.3\bin\psql.exe -U postgres -c 'SELECT 
COUNT(*)-1 FROM pg_stat_activity;'

C:\WINDOWS\Temp>c:\Programme\PostgreSQL\9.3\bin\psql.exe -U postgres -c 'SELECT 
datname, usename, query FROM pg_stat_activity;'

-- Jim