From: | "Christian Sengstock" <csengstock(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: broken restore.sql script !? |
Date: | 2006-02-22 18:03:06 |
Message-ID: | febbf1590602221003h67c8ee38v@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
hi again,
2006/2/22, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> "Christian Sengstock" <csengstock(at)gmail(dot)com> writes:
> > The function is created outside of the 'geo' schema, but after that, the
> > 'alter function' statement tries to alter the function inside of the
> 'geo'
> > schema.
This is pg_dump's normal method of operation. There should have been a
> "SET search_path = geo, pg_catalog;" command somewhere before the
> excerpt you gave.
does that mean a prior "SET search_path = geo, pg_catalog;" would create the
function inside of the geo schema ? i have this setting but it's not working
for me, despite the function is in the public schema.
i use /> psql -d mydb -U user -f restore.sql
to restore it. Could the behaviour be different when using 'pg_restore' ?
thanx,
chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-02-22 18:59:35 | Re: broken restore.sql script !? |
Previous Message | Jeff Frost | 2006-02-22 17:23:39 | Re: WAL recovery |