access), postgres installation directory (read+execute mostly), and
in some cases also for root drive of cluster data directory (read access).
Best regards,
Krystian Bigaj
On 24 July 2014 07:51, Kalai R softlinne...@gmail.com wrote:
Thank You so much Krystian Bigaj.
Since last 2 years I had suffering this problem. But today I got solution
from you.
I am developing .Net application with Postgres.
I am using WCF service (host as windows service) to connect
of this pg_console_handler won't be called (so no
processing CTRL_SHUTDOWN_EVENT by any Postgress process).
Best regards,
Krystian Bigaj
On 12 June 2014 15:59, boca2608 boca2...@gmail.com wrote:
Krystian Bigaj replied this in a separate email, which led to some
interesting information that I would like to share in this mailing list.
He suggested the use of the Process Monitor app to log the process events
during the startup
solved all of that problems.
PS. I'm running PG under NetworkService account, but I'm not using
installer from EDB or even pg_ctl (shutdown code is buggy, but it's a
postgres.exe issue).
Best regards,
Krystian Bigaj
of 1,01MB (so 1MB of string data,
and some pg header/data).
If I turn off SSL Compression data transfer between postgres and pgadmin is
still 1,01MB (but in properties I see SSL Compression=no)
It looks like SSL compression doesn't work, or am I missing something?
Best regards,
Krystian Bigaj
Thanks! That would make sense why it doesn't work on Windows.
Do you know why PG build for Windows ships zlib support enabled for PG
(mostly pg_dump/pg_restore) but disabled for OpenSSL?
Best regards,
Krystian Bigaj
On 8 May 2014 17:28, Terence Ferraro terencejferr...@gmail.com wrote:
You
of this I wrongly
assumed that OpenSSL is build with zlib too. Additionally that
Encryption=SSL encrypted and SSL Compression=yes in pgAdmin made me
think that it's a bug in PG.
Best regards,
Krystian Bigaj
On 8 May 2014 17:28, Terence Ferraro terencejferr...@gmail.com wrote:
You mentioned you
