Maybe the issue, for the momtent, could be avoided modifying the shared heap
for sessions on Windows. But I don't really have idea how much to increase
or decrease the values. Try and error? But, inside the opened Windows
sessions nothing alerts of a heap exaust so could be unpredictable how much
Page dp...@pgadmin.org
On Sun, Aug 29, 2010 at 12:05 PM, Magnus Hagander mag...@hagander.net
wrote:
On Thu, Aug 26, 2010 at 22:59, Cristian Bittel cbit...@gmail.com
wrote:
I still believe this exit code 128 is related to pgAdmin opened during
the
clossing session on Remote Desktop. I
I still believe this exit code 128 is related to pgAdmin opened during the
clossing session on Remote Desktop. I have a Windows user login wich is not
administrator just no privileged user, it cannot start/stop services, just
monitoring. With pgAdmin window opened inside my disconected session, as
From the users point of view, this could be a Windows or AV issue, but just
stops Postgres service, does not affect or interfire on Windows stability or
AV stability, instead it affect your product. So if you can improve the
stability of the service (and data integrity at the most) it could be a
