From: | Tomasz Szypowski <tomasz(dot)szypowski(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: could not fork autovacuum worker process: No error |
Date: | 2017-04-02 17:51:59 |
Message-ID: | CACmJi2Kz-R2bG5GU_+Cb3NhNwN+9-bH_5fW+px4HXMF7+4sLJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello guys,
I build PostgreSQL 32 bit on Windows with Microsoft Visual Studio 8.
I don`t see any config.pl file, Do you mean config_default.pl? If yes, than
the only module, that I activiate is zlib. I don`t need any extension like
openssl, xml and so on.
Regards
Thomas
2017-04-02 17:58 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> > I think that the OP here is asking for a solution where our shared
> > memory implementation is not messed up with ASLR enabled. And we don't
> > have a clear solution for that yet.
>
> Yeah. I don't know anything about the address space layout under Windows,
> but it occurs to me to ask how much of the address space their version of
> ASLR thinks it can chew up. Maybe we could fix this by explicitly asking
> for the shmem block to be mapped at the top of memory always, or something
> along that line. Perhaps it would only be fixable that way under Win64,
> but that would still be a good step forward.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2017-04-02 22:08:56 | Re: could not fork autovacuum worker process: No error |
Previous Message | Tom Lane | 2017-04-02 15:58:57 | Re: could not fork autovacuum worker process: No error |