| From: | Sergiy Zuban <s(dot)zuban(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postgres_fdw - push down conditionals for ENUMs |
| Date: | 2015-06-04 21:30:08 |
| Message-ID: | CAGz8fGbmdMOLApH1nAf=088QOho=iCOG82pWypYP64BGnR0Y3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> > 1. Is there any plans to add "non-strict mode" (configurable via options
>> on
>> > server/table/column level) to allow pushing down conditions for all data
>> > types?
>>
>> No. You might as well call it a "return random answers" mode.
>>
>
> Its bad. I think most users would be happy to have "auto discovery" mode
> when foreign table fetches all required meta info to act like original
> table.
>
Since 9.5 has IMPORT FOREIGN SCHEMA don't you think that foreign tables can
be marked as "imported". This 100% guarantees that all user-defined data
types/domains (including ENUMs) imported as well. It should be safe to push
down conditionals for imported types. Does it makes sense?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-06-04 21:35:00 | Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |
| Previous Message | Robert Haas | 2015-06-04 21:29:51 | Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |