Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 3F1A92E006F for ; Mon, 28 Apr 2008 04:30:18 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 67766-10 for ; Mon, 28 Apr 2008 04:30:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from pih-relay06.plus.net (pih-relay06.plus.net [212.159.14.133]) by developer.postgresql.org (Postfix) with ESMTP id 564AA2E0089 for ; Mon, 28 Apr 2008 04:30:13 -0300 (ADT) Received: from [84.51.143.99] (helo=server3.office.archonet.com) by pih-relay06.plus.net with esmtp (Exim) id 1JqNoQ-0000Hn-1c; Mon, 28 Apr 2008 08:30:10 +0100 Received: from [192.168.1.36] (dell36.office.archonet.com [192.168.1.36]) by server3.office.archonet.com (Postfix) with ESMTP id 3FCD1274064; Mon, 28 Apr 2008 08:30:09 +0100 (BST) Message-ID: <48157D01.5050405@archonet.com> Date: Mon, 28 Apr 2008 08:30:09 +0100 From: Richard Huxton User-Agent: Thunderbird 2.0.0.12 (X11/20080213) MIME-Version: 1.0 To: chester c young CC: Tom Lane , sql pgsql Subject: Re: psql: no schema info References: <213749.31261.qm@web54304.mail.re2.yahoo.com> In-Reply-To: <213749.31261.qm@web54304.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: e0a4551e927a630703f8c11c5dbe35be X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/210 X-Sequence-Number: 30749 chester c young wrote: > using 8.2 and 8.3 > > here's (psychological) problem as I see it: > > # set search_path=old_schema; > # > # create sequence new_schema.seq1; > # > # create table new_schema.table1( > # col1 integer default nextval( 'seq1' ) > # ); > > using old_schema.seq1, not new_schema.seq1 > > and imho to make matters more difficult to troubleshoot: > > # \dt table1 -> does not show which schema for seq1 Must admit I thought you were wrong, but having tested it, I think I see what you mean. If the schema in question is in the search_path then it doesn't get displayed. If you've forgotten what your search_path is set to then that can cause confusion. Not a problem I see much of since I very rarely change my search_path. I refer to schema.table by preference. -- Richard Huxton Archonet Ltd