From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?Q?G=C3=BCnce_Kaya?= <guncekaya14@gmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Postgresql FDW - some difference between remote and target table
 structure
In-reply-to: 
 <CAAV2-mXE87u0n86et4+3un4pR9C5Sh7APAANwmzRn=Gc=dCxSQ@mail.gmail.com>
References: 
 <CAAV2-mXE87u0n86et4+3un4pR9C5Sh7APAANwmzRn=Gc=dCxSQ@mail.gmail.com>
Comments: In-reply-to =?UTF-8?Q?G=C3=BCnce_Kaya?= <guncekaya14@gmail.com>
	message dated "Thu, 05 Oct 2017 13:44:59 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28775.1507211735.1@sss.pgh.pa.us>
Date: Thu, 05 Oct 2017 09:55:35 -0400
Message-ID: <28776.1507211735@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

=?UTF-8?Q?G=C3=BCnce_Kaya?= <guncekaya14@gmail.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


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin