[HACKERS] Extend file_fdw wrapper
Attached patch. pasman 0001-Extend-file_fdw-wrapper.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Extend file_fdw wrapper
2011/10/10 pasman pasmański pasma...@gmail.com: Attached patch. ... and what are these new options intended to do? -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935 EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Extend file_fdw wrapper
At a quick glance, this patch seems to have an issue about priority. Which value is used if an option has been set both on a foreign table and a foreign server? Also I think documents and regression tests would be required for this kind of change. Regards, -- Shigeru Hanada -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Extend file_fdw wrapper
On Mon, Oct 10, 2011 at 10:51:03PM +0900, Shigeru Hanada wrote: At a quick glance, this patch seems to have an issue about priority. Which value is used if an option has been set both on a foreign table and a foreign server? I believe that the finer-grained setting should always override the coarser, so in this case, the setting for the table should take precedence over the setting for the server. Also I think documents and regression tests would be required for this kind of change. +1 :) Cheers, David. -- David Fetter da...@fetter.org http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Extend file_fdw wrapper
On 10/10/2011 09:51 AM, Shigeru Hanada wrote: At a quick glance, this patch seems to have an issue about priority. Which value is used if an option has been set both on a foreign table and a foreign server? Also I think documents and regression tests would be required for this kind of change. I'm not even sure I understand why we should want this anyway. The closest analog I can think of to a more conventional server is that the whole file system is the foreign server, and there just don't seem to be any relevant options at that level. All the options being supplied seem much saner left as just foreign table options. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Extend file_fdw wrapper
Hi. Current behaviour is error message when foreign table and foreign server have the same option defined. I don't know how to write regression test, may i read about it somewhere? -- pasman -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Extend file_fdw wrapper
On Mon, Oct 10, 2011 at 10:23:51AM -0400, Andrew Dunstan wrote: On 10/10/2011 09:51 AM, Shigeru Hanada wrote: At a quick glance, this patch seems to have an issue about priority. Which value is used if an option has been set both on a foreign table and a foreign server? Also I think documents and regression tests would be required for this kind of change. I'm not even sure I understand why we should want this anyway. The closest analog I can think of to a more conventional server is that the whole file system is the foreign server, and there just don't seem to be any relevant options at that level. All the options being supplied seem much saner left as just foreign table options. You raise an excellent point, which is that there probably should be options at that level which override the (settable) generic file_fdw options. Cheers, David. -- David Fetter da...@fetter.org http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Extend file_fdw wrapper
On 10/10/2011 11:59 AM, David Fetter wrote: On Mon, Oct 10, 2011 at 10:23:51AM -0400, Andrew Dunstan wrote: On 10/10/2011 09:51 AM, Shigeru Hanada wrote: At a quick glance, this patch seems to have an issue about priority. Which value is used if an option has been set both on a foreign table and a foreign server? Also I think documents and regression tests would be required for this kind of change. I'm not even sure I understand why we should want this anyway. The closest analog I can think of to a more conventional server is that the whole file system is the foreign server, and there just don't seem to be any relevant options at that level. All the options being supplied seem much saner left as just foreign table options. You raise an excellent point, which is that there probably should be options at that level which override the (settable) generic file_fdw options. That's not my point at all. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
