| From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: CommitFest 2011-01 as of 2011-02-04 |
| Date: | 2011-02-15 08:31:41 |
| Message-ID: | AANLkTimwGyCQC_a9ARfJKJ+wd7QSUjLfA-ncLVXtmk4i@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 15, 2011 at 01:27, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> However, file_fdw is in pretty serious trouble because (1) the copy
> API patch that it depends on still isn't committed and (2) it's going
> to be utterly broken if we don't do something about the
> client_encoding vs. file_encoding problem; there was a patch to do
> that in this CF, but we gave up on it.
Will we include the copy API patch in 9.1 even if we won't have file_fdw?
Personally, I want to include the APIs because someone can develop file_fdw
as a third party extension for 9.1 using the infrastructure. The extension
will lack of file encoding support, but still useful for many cases.
--
Itagaki Takahiro
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-02-15 08:38:37 | Re: pageinspect's infomask and infomask2 as smallint |
| Previous Message | Heikki Linnakangas | 2011-02-15 08:19:08 | Re: SSI bug? |