Thanks Scott,
I'll try that out; I hope this would solve my problem...
Regards,
Samba
On Tue, Aug 7, 2012 at 8:30 PM, Scott Marlowe wrote:
> On Tue, Aug 7, 2012 at 7:15 AM, Samba wrote:
> > Thanks Gabriele for those pointers,
> >
> >
On Tue, Aug 7, 2012 at 7:15 AM, Samba wrote:
> Thanks Gabriele for those pointers,
>
> I could now narrow it down to two things:
>
> "system_data" user logging into other databases [one of those may be the
> default 'postgres'] which does not have "system_data" schema
> other users [like 'postgres
Hi all,
I now realize that the issue is indeed occurring when users who have
"system_data" in their search_path log in to other databases that does not
have that schema.
Could someone explain how to "add schema(s) into search_path for a database
[not to user/role] irrespective of whichever user
Samba wrote:
> I'm seeing some weired errors in the postgres logs after upgrading
> to postgres-9.1(.3) about the schema added by default to search patch
>
> WARNING: invalid value for parameter "search_path": "system_data"
> DETAIL: schema "system_data" does not exist
>
> We do have a user nam
Samba writes:
> I'm seeing some weired errors in the postgres logs after upgrading to
> postgres-9.1(.3) about the schema added by default to search patch
> WARNING: invalid value for parameter "search_path": "system_data"
> DETAIL: schema "system_data" does not exist
> ...
> Could anyone sugges
Thanks Gabriele for those pointers,
I could now narrow it down to two things:
1. "system_data" user logging into other databases [one of those may be
the default 'postgres'] which does not have "system_data" schema
2. other users [like 'postgres'] logging into their own or even other
Hi Samba,
first: do not worry, it is perfectly normal.
On Tue, 7 Aug 2012 16:25:14 +0530, Samba wrote:
Hi all,
I'm seeing some weired errors in the postgres logs after upgrading to
postgres-9.1(.3) about the schema added by default to search patch
WARNING: invalid value for parameter "sea
