Re: copy_file_range is now a Linux kernel call

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: copy_file_range is now a Linux kernel call
Date: 2018-01-03 08:46:44
Message-ID: 20180103084644.766glmry6xpjpzez@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-01-02 23:34:47 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2018-01-02 23:08:05 -0500, Tom Lane wrote:
> >> Bleah --- "rwnd" is unpronounceable and not an abbreviation we're
> >> currently using anywhere. If we go that way, let's brave carpal tunnel
> >> syndrome by calling it "rewind_copy_file_range". But I'm not that
> >> happy with any of these.
>
> > rewind_copy_file_range works for me.
>
> >> Maybe go with copy_file_chunk like e2fsprogs did?
>
> > -0.2 - don't think it hurts to signal this isn't a general function.
>
> Fair enough. You want to do the honors, or shall I?

Will do tomorrow morning, unless you beat me to it over there on the
cold coast.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Sharma 2018-01-03 08:52:14 Do we really need to switch to per-tuple memory context in ATRewriteTable() when Table Rewrite is not happening
Previous Message Haribabu Kommi 2018-01-03 07:48:07 Re: Enhance pg_stat_wal_receiver view to display connected host