| From: | Günce Kaya <guncekaya14(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Postgresql FDW - some difference between remote and target table structure |
| Date: | 2017-10-05 14:19:45 |
| Message-ID: | CAAV2-mU5iCeebXjfUSzu4PmzgmL6YmyHXCoQVXaQ8yWSCzj=mQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello Tom,
I appreciate to your response. It’s clear now to me.
Regards,
Gunce
On 5 Oct 2017 Thu at 16:55 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> =?UTF-8?Q?G=C3=BCnce_Kaya?= <guncekaya14(at)gmail(dot)com> writes:
> > Why there is some difference between FDW and target database? Is there
> > anyone who can explain it?
>
> Either the foreign table was created without that column to begin with,
> or the column was added to the remote table later and the foreign table
> wasn't updated to match. Foreign tables don't magically track what is
> on the remote server; they just have the set of columns you told the
> local server they should have.
>
> regards, tom lane
>
--
Gunce Kaya
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Major | 2017-10-05 14:53:57 | Additional checks for orphaned files |
| Previous Message | Tom Lane | 2017-10-05 13:55:35 | Re: Postgresql FDW - some difference between remote and target table structure |