Inconvenience of pg_read_binary_file() - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Inconvenience of pg_read_binary_file()
Date
Msg-id 20220607.160520.1984541900138970018.horikyota.ntt@gmail.com
Whole thread Raw
Responses Re: Inconvenience of pg_read_binary_file()
List pgsql-hackers
If I want to read a file that I'm not sure of the existence but I want
to read the whole file if exists, I would call
pg_read_binary_file('path', 0, -1, true) but unfortunately this
doesn't work.

Does it make sense to change the function so as to accept the
parameter specification above? Or the arguments could be ('path',
null, null, true) but (0,-1) is simpler considering the
characteristics of the function.

(We could also rearrange the the parameter order as "filename,
missing_ok, offset, length" but that is simply confusing..)

If it is, pg_read_file() is worth receive the same modification and
I'll post the version containing doc part.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: Chinmay Kanchi
Date:
Subject: An inverted index using roaring bitmaps
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: pg_rewind: warn when checkpoint hasn't happened after promotion