| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Xiaobo Gu *EXTERN*" <guxiaobo1982(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: File size consideration of file_fdw in PostgreSQL |
| Date: | 2013-06-24 08:19:54 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17BB5A27@ntex2010a.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Xiaobo Gu wrote:
> We have very large files in size will be created as external tables in PostgreSQL via file_fdw, we
> have the following considerations:
> 1. Can file_fdw handle files with size large than the size of RAM in the server.
That shouldn't be a problem.
> 2. Will file_fdw scan the full file every time when the external table is queried, even we have
> "where" clause to narrow to a subset of rows , as the file_fdw doesn't have a server engine.
Yes, the complete file will be read whenever the foreign
table is queried.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2013-06-24 08:43:00 | Re: WAL archiving not starting at the beginning |
| Previous Message | Martin Durao | 2013-06-24 08:00:15 | Get / Set Composite Type Fields within triggers |