| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgconfbug(at)yopmail(dot)com, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #12884: configure script fails on a platform with /tmp directory read only |
| Date: | 2016-08-02 18:06:30 |
| Message-ID: | 142579e2-c123-b7e3-2ec3-808b429a84b8@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 3/20/15 1:02 PM, pgconfbug(at)yopmail(dot)com wrote:
> Bug reference: 12884
> Logged by: X
> Email address: pgconfbug(at)yopmail(dot)com
> PostgreSQL version: 9.0.19
> Operating system: Linux SLES 10 SP2
> Description:
>
> On a platform intentionally setup with a /tmp directory readonly but with a
> TMPDIR environment variable pointing to a writable location the configure
> script fails detecting a non thread safe platform.
This was fixed in PostgreSQL 9.2.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-02 19:30:42 | Re: BUG #14273: Tuple concurently updated error while creating function using async call from node js with postgresq |
| Previous Message | Alvaro Herrera | 2016-08-02 18:00:11 | Re: BUG #14273: Tuple concurently updated error while creating function using async call from node js with postgresq |