| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Tomasz Szypowski <tomasz(dot)szypowski(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: could not fork autovacuum worker process: No error |
| Date: | 2017-04-03 06:51:06 |
| Message-ID: | 20170403065106.GA2624300@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Apr 02, 2017 at 06:08:56PM -0400, Noah Misch wrote:
> On Sun, Apr 02, 2017 at 07:51:59PM +0200, Tomasz Szypowski wrote:
> > I build PostgreSQL 32 bit on Windows with Microsoft Visual Studio 8.
>
> That version number is ambiguous. From the command prompt in which you build
> PostgreSQL, what is the output of these two commands?
>
> cl
> systeminfo | findstr /B OS
>
> If you build PostgreSQL on one system and run it on a different system, what
> is the output of "systeminfo | findstr /B OS" on the runtime system?
Also, could you run a test workload that reproduces the problem against a
postgres.exe built with the attached patch? This will dump details of your
memory postgres.exe memory map to the log, hopefully giving a clue about the
source of the trouble.
| Attachment | Content-Type | Size |
|---|---|---|
| w32-memory-map-v1.patch | text/plain | 4.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ygutfreund | 2017-04-03 14:59:09 | BUG #14610: pgAdmin getting connection timeout (local client to local server) |
| Previous Message | Paul Coyne | 2017-04-02 23:55:39 | Re: BUG #14609: ON CONSTRAINT (aka UPSERT) code fails when excluded.<columname> used in calculation. |