| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Samba <saasira(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: warnings about invalid "search_path" |
| Date: | 2012-08-07 14:19:13 |
| Message-ID: | 16756.1344349153@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Samba <saasira(at)gmail(dot)com> 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 suggest what could be wrong with my setup and how to get past
> it?
From the 9.1.4 release notes:
* Ignore missing schemas during non-interactive assignments of search_path (Tom Lane)
This re-aligns 9.1's behavior with that of older branches. Previously
9.1 would throw an error for nonexistent schemas mentioned in
search_path settings obtained from places such as ALTER DATABASE SET.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2012-08-07 14:20:52 | Re: warnings about invalid "search_path" |
| Previous Message | Pavel Stehule | 2012-08-07 14:19:04 | Re: Are stored procedures always kept in memory? |