| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| Date: | 2018-09-17 18:30:40 |
| Message-ID: | 99abad95-2b1a-32ea-50bb-416747fb87c4@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 09/17/2018 12:13 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
>> On 09/17/2018 10:48 AM, Tom Lane wrote:
>>> We've got a bit of a timing problem because we want to wrap 11beta4/rc1
>>> (still TBD) in a few hours. I'll take a look and see if I can push a
>>> quick fix before that.
>> When you do I'll start a bowerbird run to check it.
> Pushed, please test.
>
> I think there's a general issue here of exactly how we want pgwin32_fopen
> to behave, but the immediate problem is best fixed by making pgbench deal
> with Windows newlines more thoroughly.
>
>
Tests are still running, but it's past the pgbench stage on HEAD, so I
think we're good.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-09-17 22:00:58 | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| Previous Message | Tom Lane | 2018-09-17 17:16:44 | pgsql: Fix parsetree representation of XMLTABLE(XMLNAMESPACES(DEFAULT . |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2018-09-17 19:32:16 | Re: Collation versioning |
| Previous Message | Pavel Stehule | 2018-09-17 18:27:23 | Re: Stored procedures and out parameters |