I have a script that looks like this:
BEGIN; SET client_min_messages TO warning; SET search_path TO geo; CREATE TABLE continents ( code CHARACTER(2) PRIMARY KEY, continent TEXT NOT NULL );
I ran this against a coordinator, and it seemed to work. But when I tried to select from the table, XC said it could not be found. \d geo.continents shows it, but only on the coordinator on which I ran the script. If I connect to any other coordinator or any data node, the continents table is in the public schema rather than the geo schema.
Bug? I don't see any mentinon of SET not being distributed in the SET docs. I can work around it by schema-qualifying objects, but would rather not have to.
Log in to post a comment.