Thank you for the message Tom; sounds great. I'll try that out, will check
on the planner's resultant behavior and email back.
Peter
On Sat, May 23, 2015 at 12:35 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Peter Swartz peter.goodings.swa...@gmail.com writes:
suppose the foreign database adds a
Thank you for the note Ian. I definitely see your point about the onus
being on the local database to maintain the definition of the remote
table. Do you or anyone have this list have any experience with the
resulting behavior if the definition of the enum were to become out of sync
between the
Peter Swartz peter.goodings.swa...@gmail.com writes:
suppose the foreign database adds a value to the enum, and the foreign
table now has rows with this new value, while the local definition of the
enum remains unchanged. Obviously, the appropriate action on my part is to
maintain consistency
On 21/05/15 04:23, Peter Swartz wrote:
I'm creating a foreign table (foo_table) in database_a. foo_table lives in
database_b.foo_table has an enum (bar_type) as one of its columns. Because
this enum is in database_b, the creation of the foreign table fails in
database_a. database_a doesn't
