Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id DBF4C9FB33B for ; Mon, 23 Oct 2006 17:46:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 12625-04 for ; Mon, 23 Oct 2006 17:46:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from community1.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id A9B7D9FB2D2 for ; Mon, 23 Oct 2006 17:46:42 -0300 (ADT) Received: from [192.168.27.150] ([12.38.10.44]) (authenticated bits=0) by community1.commandprompt.com (8.13.5.20060308/8.13.5/Debian-3ubuntu1.1) with ESMTP id k9NKkdCr022420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 23 Oct 2006 13:46:41 -0700 Message-ID: <453D2A2E.6040500@dunslane.net> Date: Mon, 23 Oct 2006 16:46:38 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.6) Gecko/20060804 Fedora/1.0.4-0.5.1.fc5 SeaMonkey/1.0.4 MIME-Version: 1.0 To: Zdenek Kotala CC: Tom Lane , pgsql-hackers@postgresql.org Subject: Re: COPY does not work with regproc and aclitem References: <453D1B73.2050906@sun.com> <453D1EBF.5070506@dunslane.net> <453D201E.3070202@sun.com> <28143.1161634972@sss.pgh.pa.us> <453D26A9.70702@sun.com> In-Reply-To: <453D26A9.70702@sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.076 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, SPF_HELO_SOFTFAIL, SPF_SOFTFAIL X-Spam-Level: ** X-Archive-Number: 200610/1244 X-Sequence-Number: 93141 Zdenek Kotala wrote: > Tom Lane wrote: > >> The right way to implement pg_upgrade is to transfer the catalog data >> at the SQL-command level of abstraction, ie, "pg_dump -s" and reload. > > I'm not sure if it is important, but I think that preserve OID is > important and SQL level does not allow set OID. > > Does it matter in any case other than where it refers to an on-disk object? And does that need anything other than a fixup to pg_class::relfilenode? cheers andrew