Wed Apr 8 16:34:35 PDT 2009
- Previous message: [Slony1-general] 'public' schema problem
- Next message: [Slony1-general] First public release of slony1-ctl
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > This seems rather curious; there are no references to the "public" schema > in Slony-I itself (although there are in test scripts). > > There is also no such error message within Slony-I itself as "No schema > available to setup objects". This was not exactly the error but it was something like this, I will try to replicate the same again and will paste the exact one again when I get time. > > > That doesn't mean you didn't see it - just that it would have had to be > induced somewhere else. I also don't see it in PostgreSQL code (in HEAD, > but I doubt that's material). > > The only plausible thing that comes to mind would be that perhaps the user > you connected as had some vestigal reference to "public" as being its > default schema, so that when the user connected, something was left devoid > of a place to create objects that weren't tied to a specific schema. This is true as the user had the default schema set to public as it was the default 'postgres' user I was using so I am pretty sure it can be linked to this as it didnt have any schema to create objects. -- = Shoaib Mir -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20090409/= d42d352e/attachment.htm
- Previous message: [Slony1-general] 'public' schema problem
- Next message: [Slony1-general] First public release of slony1-ctl
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list