From: | Li Japin <japinli(at)hotmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: file_fdw vs relative paths |
Date: | 2020-08-25 07:28:41 |
Message-ID: | 70C4CA98-1C0D-426B-9814-92569A5331B6@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Aug 25, 2020, at 8:26 AM, Bruce Momjian <bruce(at)momjian(dot)us<mailto:bruce(at)momjian(dot)us>> wrote:
Yes, I tested back to 9.5 too:
CREATE EXTENSION file_fdw;
CREATE SERVER pgconf FOREIGN DATA WRAPPER file_fdw;
CREATE FOREIGN TABLE pgconf (line TEXT) SERVER pgconf OPTIONS ( filename
'postgresql.conf', format 'text', delimiter E'\x7f' );
SELECT * FROM pgconf;
# -----------------------------
# PostgreSQL configuration file
# -----------------------------
#
# This file consists of lines of the form:
…
The file_fdw extension was introduced by commit 7c5d0ae7078456bfeedb2103c45b9a32285c2631,
and I tested it supports relative paths. This is a doc bug.
--
Japin Li
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2020-08-25 07:32:42 | Re: Row estimates for empty tables |
Previous Message | Pavel Stehule | 2020-08-25 06:57:27 | Re: proposal - function string_to_table |