Re: [Postgres-xc-developers] SET search_path Not Distributed

[Koichi S. <koi...@gm...>]

Hmm.   There could be two candidates of the cause.

One is, as you mentioned, set propagation.   SET is handled within the
connection pooler in general way so I think this is less probable.
Another is XC-internal alias handling, which took much to fix
especially in the merge with PG master before 9.3 was cut.

Regards;
---
Koichi Suzuki


2014-01-31 David E. Wheeler <da...@ju...>:
> On Jan 30, 2014, at 5:04 PM, David E. Wheeler <da...@ju...> wrote:
>
>> I can work around it by schema-qualifying objects, but would rather not have to.
>
> Another search_path issue: If you have schema-qualified a data type in a table column, queries will fail against that table:
>
>     dwheeler=# create schema bar;
>     CREATE SCHEMA
>     dwheeler=# create type bar.lol as enum ('a', 'b');
>     CREATE TYPE
>     dwheeler=# create table bar.hey (lol bar.lol) DISTRIBUTE BY REPLICATION;
>     CREATE TABLE
>     dwheeler=# select * from bar.hey;
>     ERROR:  type "lol" does not exist
>
> I guess the workaround would be to set the search_path to include all my schemas on in all the coordinator and data node postgresql.conf files?
>
> Thanks,
>
> David
>
>
> ------------------------------------------------------------------------------
> WatchGuard Dimension instantly turns raw network data into actionable
> security intelligence. It gives you real-time visual feedback on key
> security issues and trends.  Skip the complicated setup - simply import
> a virtual appliance and go from zero to informed in seconds.
> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers