On 22 September 2016 at 20:02, Yury Zhuravlev
wrote:
> On четверг, 15 сентября 2016 г. 19:09:16 MSK, Tom Lane wrote:
>>
>> Robert Haas writes:
>>>
>>> On Thu, Sep 15, 2016 at 11:01 AM, Anastasia Lubennikova
>>> wrote:
What do you think about moving stuff from pg_upgrade/file.c to
On четверг, 15 сентября 2016 г. 19:09:16 MSK, Tom Lane wrote:
Robert Haas writes:
On Thu, Sep 15, 2016 at 11:01 AM, Anastasia Lubennikova
wrote:
What do you think about moving stuff from pg_upgrade/file.c
to storage/file/
to allow reuse of this code? I think it'll be really helpful
for devel
Robert Haas writes:
> On Thu, Sep 15, 2016 at 11:01 AM, Anastasia Lubennikova
> wrote:
>> What do you think about moving stuff from pg_upgrade/file.c to storage/file/
>> to allow reuse of this code? I think it'll be really helpful for developers
>> of contrib modules
>> like backup managers.
> W
On Thu, Sep 15, 2016 at 11:01 AM, Anastasia Lubennikova
wrote:
> What do you think about moving stuff from pg_upgrade/file.c to storage/file/
> to allow reuse of this code? I think it'll be really helpful for developers
> of contrib modules
> like backup managers.
Well, storage/file is backend an
Hi, hackers!
Do we have any standard set of functions to operate with files?
I mean link(), copy(), rename(), unlink(), ftruncate() and so on.
Mostly I worry about the first two since they have different
implementation on Windows.
I found a couple of functions in src/backend/storage/file/copydir