The following bug has been logged online:
Bug reference: 6011
Logged by: MauMau
Email address: maumau...@gmail.com
PostgreSQL version: 8.3.12/9.0.3
Operating system: Windows XP and Vista
Description:Some extra messages are output in the event log at
PostgreSQL startup
On Fri, May 6, 2011 at 16:08, MauMau wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6011
> Logged by: MauMau
> Email address: maumau...@gmail.com
> PostgreSQL version: 8.3.12/9.0.3
> Operating system: Windows XP and Vista
> Description: Some ext
The following bug has been logged online:
Bug reference: 6010
Logged by: alex
Email address: alexandr.kas...@gmail.com
PostgreSQL version: 9.1 beta1
Operating system: snow leopard
Description:booting problem
Details:
after changing sysctl.conf values and rebooting (
The following bug has been logged online:
Bug reference: 6012
Logged by: Jai Kumar Shamra
Email address: sharma.jaiku...@gmail.com
PostgreSQL version: 8.4
Operating system: Windows XP Professional SP2
Description:Automatically generated sequence number jumps.
Details:
Magnus Hagander writes:
> On Fri, May 6, 2011 at 16:08, MauMau wrote:
>> The problem is that the following messages are always output in the event
>> log at PostgreSQL startup, even when the log_destination parameter doesn't
>> contain 'eventlog':
>>
>> [message 1]
>> Waiting for server startup.
"Jai Kumar Shamra" wrote:
> Description:Automatically generated sequence number jumps.
> We are facing problem of automatically sequence number changes in
> increasing order, why?
Probably transactions rolled back or someone used the setval
function. From the manual:
http://www.po
Magnus Hagander writes:
Any events that happen before we have opened the regular logfile will
be written to the eventlog if the server is running as a Windows
service. There is no way to turn that off (other than removing the
code and recompiling, of course). If we didn't send those to the
event
