On Wed, Feb 22, 2012 at 7:28 AM, <michal.rakoczy@sb-betting.com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: =C2=A0 =C2=A0 =C2=A06481
> Logged by: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Micha=C5=82 Rakoczy
> Email address: =C2=A0 =C2=A0 =C2=A0michal.rakoczy@sb-betting.com
> PostgreSQL version: 9.0.5
> Operating system: =C2=A0 Windows Server 2008 R2 Enterprise x64 SP1
> Description:
>
> Hi
>
> I'm struggling with this problem since few days.
>
> My environment contains two PostgreSQL instances with build-in streaming
> replication. Master host is being queried by JBoss application server, wh=
en
> slave works in read-only mode, as db backup in case of master host crash.
>
> Suddenly PostgreSQL shuts down unexpectedly without any reason.
>
> Event viewer log :
>
> Windows detected your registry file is still in use by other applications=
or
> services. The file will be unloaded now. The applications or services that
> hold your registry file may not function properly afterwards.
>
> =C2=A0DETAIL -
> =C2=A02 user registry handles leaked from
> \Registry\User\S-1-5-21-1897005561-2437030572-477490838-1005:
> Process 1400 (\Device\HarddiskVolume3\Windows\System32\conhost.exe) has
> opened key
> \REGISTRY\USER\S-1-5-21-1897005561-2437030572-477490838-1005\Control
> Panel\International
> Process 9020 (\Device\HarddiskVolume5\PostgreSQL\9.0\bin\postgres.exe) has
> opened key
> \REGISTRY\USER\S-1-5-21-1897005561-2437030572-477490838-1005\Control
> Panel\International
I think we need to see the PostgreSQL log, rather than this.
--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company