Re: File system operations. - Mailing list pgsql-hackers

From Yury Zhuravlev
Subject Re: File system operations.
Date
Msg-id 4f6c2489-02ef-4efb-8525-864f50cf55ab@postgrespro.ru
Whole thread Raw
In response to Re: File system operations.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: File system operations.  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On четверг, 15 сентября 2016 г. 19:09:16 MSK, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Thu, Sep 15, 2016 at 11:01 AM, Anastasia Lubennikova
>> <a.lubennikova@postgrespro.ru> 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 and pg_upgrade is frontend.  If you want
>> to reuse the same code for both it's got to go someplace else.
>
> Also, to the extent that it's important to use those wrappers rather
> than libc directly, it's because the wrappers are tied into backend
> resource management and error handling conventions.  I don't see how
> you convert that into code that also works in a frontend program,
> or what the point would be exactly.

Maybe we should towards to framework ecosystem. I mean, developers of third
party tools must use maximum same api what in backend.

--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-hackers by date:

Previous
From: Kuntal Ghosh
Date:
Subject: Re: pgbench - compute & show latency consistently
Next
From: Amit Kapila
Date:
Subject: Re: Parallel sec scan in plpgsql