From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Ravi Krishna <sravikrishna(at)comcast(dot)net> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Oracle vs. PostgreSQL - a comment |
Date: | 2020-06-02 21:16:59 |
Message-ID: | 20200602211659.GB6680@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
* Ravi Krishna (sravikrishna(at)comcast(dot)net) wrote:
> > Eh, that's something that I think we should be looking at supporting, by
> > using FDWs, but I haven't tried to figure out how hard it'd be.
>
> How good will that be in performance.
>
> In db2 you can do it using dblinks and that kills performance. isn't FDW something like dblink.
>
> The cool part is that in SQLServer the optimizer recognizes 3 part name and caching works also.
I'm sure there's things we can do to improve the performance of the FDW.
Not sure we'll get to a point where we are actually cacheing information
from the far side... but who knows, maybe if we arrange to have a
notification sent whenever certain objects are updated...
These things could be worked on independnetly, of course, no need to
have one done before the other.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2020-06-02 21:18:52 | Re: Oracle vs. PostgreSQL - a comment |
Previous Message | Ravi Krishna | 2020-06-02 20:49:35 | Re: Oracle vs. PostgreSQL - a comment |