X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 3566A9DCC52 for ; Wed, 22 Feb 2006 14:03:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 52785-10-2 for ; Wed, 22 Feb 2006 14:03:09 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.204]) by postgresql.org (Postfix) with ESMTP id 57D849DCC44 for ; Wed, 22 Feb 2006 14:03:06 -0400 (AST) Received: by nproxy.gmail.com with SMTP id o25so1040724nfa for ; Wed, 22 Feb 2006 10:03:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Q7lyqYHD3Gf3FTEAv3O5P4MpbhNpIIL2p41KDx0RBOi+jKjGA0ZqfkeiO64+QfQLTC7qDyn+5Q5PkU33L0TBUtcCAZt/VEQ8BLiNpIYKsK/CQ7Jh/wrfdPpDSMxFuKUW9sRUwjDsr6BE5qoLXXSeQ1GuuQFDE7xkR29/w6sR9Yw= Received: by 10.49.68.13 with SMTP id v13mr1959339nfk; Wed, 22 Feb 2006 10:03:06 -0800 (PST) Received: by 10.48.157.7 with HTTP; Wed, 22 Feb 2006 10:03:06 -0800 (PST) Message-ID: Date: Wed, 22 Feb 2006 19:03:06 +0100 From: "Christian Sengstock" To: "Tom Lane" Subject: Re: broken restore.sql script !? Cc: pgsql-admin@postgresql.org In-Reply-To: <12906.1140627604@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9081_6155425.1140631386262" References: <12906.1140627604@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.919 required=5 tests=[AWL=0.592, HTML_MESSAGE=0.001, PLING_QUERY=0.326] X-Spam-Score: 0.919 X-Spam-Level: X-Archive-Number: 200602/266 X-Sequence-Number: 20687 ------=_Part_9081_6155425.1140631386262 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline hi again, 2006/2/22, Tom Lane : > > "Christian Sengstock" writes: > > The function is created outside of the 'geo' schema, but after that, th= e > > '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 =3D geo, pg_catalog;" command somewhere before the > excerpt you gave. does that mean a prior "SET search_path =3D geo, pg_catalog;" would create = the function inside of the geo schema ? i have this setting but it's not workin= g 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 ------=_Part_9081_6155425.1140631386262 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline hi again,

2006/2/22, Tom Lane <tgl@sss.pgh.pa.us>:
"Christian Sengstock" = <csengstock@gmail.com> wr= ites:
> The function is created outside of the 'geo' schema, but after tha= t, the
> 'alter function' statement tries to alter the function insid= e of the 'geo'
> schema.
 
 

This is pg_dump's normal method = of operation.  There should have been a
"SET search_path = =3D geo, pg_catalog;" command somewhere before the
excerpt you gave. 
 
does that mean a prior "SET search_path =3D 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_re= store'  ?
 
thanx,
chris
 

 

------=_Part_9081_6155425.1140631386262--