On 4/14/15 5:49 AM, Etsuro Fujita wrote: > postgres=# create foreign table ft1 (c1 int) server myserver options > (table_name 't1'); > CREATE FOREIGN TABLE > postgres=# create foreign table ft2 (c1 int) server myserver options > (table_name 't2'); > CREATE FOREIGN TABLE > postgres=# alter foreign table ft2 inherit ft1; > ALTER FOREIGN TABLE > postgres=# select * from ft1 for update; > ERROR: could not find junk tableoid1 column > > I think this is a bug. Attached is a patch fixing this issue.
What happens when the foreign side breaks the inheritance? Does the FDW somehow know to check that fact for each query? What do you gain from having the local table have inheritance? Basically, I think we have to be very careful about implementing features that imply the local side knows something about the persisted state of the remote side (in this case, whether there's inheritance). Anything like that sets us up for synchronization problems. -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
