Re: [HACKERS] Windows service is not starting so there’s message in log: FATAL: "could not create shared memory segment “Global/PostgreSQL.851401618”: Permission denied”

On Пт, 2015-10-16 at 09:02 +0530, Amit Kapila wrote: > On Thu, Oct 15, 2015 at 8:35 PM, Dmitry Vasilyev pro.ru> wrote: > > I think that function dsm_impl_windows() with EACCES error should > > not > > do ereport() with FATAL level. It works, but it is likely to make >

Re: [HACKERS] Windows service is not starting so there’s message in log: FATAL: "could not create shared memory segment “Global/PostgreSQL.851401618”: Permission denied”

I think that function dsm_impl_windows() with EACCES error should not do ereport() with FATAL level. It works, but it is likely to make an infinite loop if the user will receive EACCES error. On Чт, 2015-10-15 at 17:46 +0300, Dmitry Vasilyev wrote: >  I’ve created 2 unprivileged users: user1

[HACKERS] Windows service is not starting so there’s message in log: FATAL: "could not create shared memory segment “Global/PostgreSQL.851401618”: Permission denied”

 I’ve created 2 unprivileged users: user1 and user2; and registered 2 services thorough pg_ctl register respectively under these 2 users. If first service is running second could not start and vice versa. Dmitry Vasilyev Postgres Professional: http://www.postgrespro.com Russian Postgres

Re: [HACKERS] Postgres service stops when I kill client backend on Windows

anyone can test it on Cygwin that wouldn't be a bad thing either. > > regards, tom lane > This patch is working for me, binaries: https://goo.gl/32j7QE (MSVC 2010, build script here:  https://github.com/postgrespro/pgwininstall). -- Dmitry Va

Re: [HACKERS] Postgres service stops when I kill client backend on Windows

ase we want to > retain shared memory handle for some purpose (future requirement) > could > be to send some signal to syslogger in restart path so that it can > release > the shared memory handle. > > > > With Regards, > Amit Kapila. > EnterpriseDB: http://www.enterprisedb.com Specified patch with "ifdef WIN32" is working for me. Maybe it’s necessary to check open handlers from replication for example? -- Dmitry Vasilyev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company

Re: [HACKERS] Postgres service stops when I kill client backend on Windows

Hello Tom! On Сб, 2015-10-10 at 10:55 -0500, Tom Lane wrote: > Dmitry Vasilyev writes: > > I have written, what service stopped. This action is repeatable. > > You can run command 'psql -c "do $$ unpack p,1x8 $$ language > > plperlu;"' > > and afte

Re: [HACKERS] Postgres service stops when I kill client backend on Windows

I have written, what service stopped. This action is repeatable. You can run command 'psql -c "do $$ unpack p,1x8 $$ language plperlu;"' and after this windows service will stop.  On Сб, 2015-10-10 at 10:23 -0500, Tom Lane wrote: > Robert Haas writes: > > On Fri, O

Re: [HACKERS] Postgres service stops when I kill client backend on Windows

. !> --> >  > Hello Dmitry > > > -Original Message- > > From: pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-owne > > r...@postgresql.org] On Behalf Of Dmitry Vasilyev > > Sent: Freitag, 9. Oktober 2015 11:52 > > To: pgsql

[HACKERS] Postgres service stops when I kill client backend on Windows

not failing. So what’s the problem? Why PostgreSQL is so strange on Windows? -- Dmitry Vasilyev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: h

Re: [HACKERS] Streaming Replication clusters and load balancing

Hi! By default, HAproxy configuration can not be changed without breaking a connection with the client :) -- Dmitry Vasilyev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company On Fri, 2015-09-18 at 12:27 +1000, James Sewell wrote: > Hello all, > > I have

Re: [HACKERS] Scaling PostgreSQL at multicore Power8

We did not got any affect on core 64 with smt = 8, and we not have a 64 -cpu x86 machine with disable HT feature. You can set scale > 1000 and with shared_buffers >> size of index pgbench_accounts_pkey. You can also increase the concurrency: not only access top of b-tree index, but also to a speci