pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Günce Kaya <guncekaya14@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgresql FDW - some difference between remote and target table structure
Date: Thu, 05 Oct 2017 09:55:35 -0400
Message-ID: <28776.1507211735@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAV2-mXE87u0n86et4+3un4pR9C5Sh7APAANwmzRn=Gc=dCxSQ@mail.gmail.com>
References: <CAAV2-mXE87u0n86et4+3un4pR9C5Sh7APAANwmzRn=Gc=dCxSQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

=?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



view thread (3+ messages)  latest in thread

Message-ID: <28776.1507211735@sss.pgh.pa.us>
Permalink:  ../28776.1507211735@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/28776.1507211735@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, guncekaya14@gmail.com
  Subject: Re: Postgresql FDW - some difference between remote and target table structure
  In-Reply-To: <28776.1507211735@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox