I think both 8.3 & 8.4 are from EnterpriseDB (the integer_datetime is 'off' at least in 8.3 which is active at the
time).
Don't hesitate too much - reinstalling binaries with dump & restore of data is not a problem whatever version you'll
sendto me.
> 2009/7/7 Wojciech Strzałka <wstrzalka@gmail.com>:
>>
>> Sorry if what i'm talking is completely silly, but
>> the error code (ERROR_INVALID_ADDRESS - 487 (0x1E7)) returned from
>> MapViewOfFileEx suggest the ShMem address is wrong. The Windows
>> error codes are usually not really helpfull but
>> can we log the UsedShmemSegAddr and UsedShmemSegID in
>> PGSharedMemoryCreate and maybe also on successful PGSharedMemoryReAttach
>> in DEBUG log level?
> We could, but I don't see how it could be wrong, as it's only set in
> PGSharedMemoryCreate and when we pass it down from postmaster to
> backend. If something we're being stomped on there, I'd expect it to
> be a more random problem.
> <reads code some more>
> Although, the reattach does get called almost immediately following
> the backend variables being read, so maybe they are getting clobbered,
> and it's pretty much always shows up in the re-mapping of the shared
> memory.
> What distribution are you running? I'll see if I can hack up a build
> with the extra debugging, but I need to get the integer_datetimes
> option right for your database.
--
Pozdrowienia,Wojciech Strzałka
