Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi
Дата
Msg-id 3883.1537200836@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Ответы Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Список pgsql-committers
Andrew Dunstan <andrew.dunstan@2ndquadrant.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.

            regards, tom lane


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Fix pgbench lexer's "continuation" rule to cope with Windowsnew
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Remove dead code from pop_next_work_item().