Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dFQPz-00052W-K5 for pgsql-sql@arkaria.postgresql.org; Mon, 29 May 2017 19:33:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dFQPz-0005m7-6o for pgsql-sql@arkaria.postgresql.org; Mon, 29 May 2017 19:33:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFQOx-0003yh-64 for pgsql-sql@postgresql.org; Mon, 29 May 2017 19:32:27 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFQOt-0005Bk-8K for pgsql-sql@postgresql.org; Mon, 29 May 2017 19:32:26 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id E772C209A1; Mon, 29 May 2017 15:32:21 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Mon, 29 May 2017 15:32:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=i6wxNxwM9dQUUOj9/C atG3GGmiS8kZ74PEpH4S4x9Sg=; b=iA8/g9Cq9sdFlp1yVMiB84FpddpRiQNJWB Nk9kR3C6UiNWacAgYuTcUmcrp0TqH+UJPQFYYKNtA1hD0jGieiYyOGWLyk/gWMIg wc8ZeSNZx9f6NFeyWHSzzY411BRgxv3tuc286iiu5jnRH8ZEkh0aFOCu4IH4tThg 4T3oe/gDCqkVPVp8NYiaT5aMA1WztwwfuBn1Wzag3vmBBaz4LYcA7RDWQgtluGqR WiLW7rPDC9cYysLBkNeNzcNO/3z4zxWUAO5l08givVofS7ZFbGn0dQYnI1u1TWUj GEfBfZMARyiAsg4P0Pu1t+uD5k3MpjyZN7Kie0OwsMaS1XC99p0g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=i6wxNxwM9dQUUOj9/CatG3GGmiS8kZ74PEpH4S4x9Sg=; b=cdQltBwy ExhmvHLLuC6znio70zbMT2oJPAGo+o0DqTM1q9GwOObr8d2nl6sOzXnwlPG0+jfl Xn+aOFiHn5KBbVLke2do0UwMai5W1O5d90JMaoZ4cpVta2ntNyy/xudwOp1GY0UN QuR3yH28Kh1sx0qWMvJ3avPDSC6P+KZOWJezRE1C1c0xiPnM5a2cxIqN54h/qDTW zC+GCFeXh9TnST/zRjFEF5ncQLraGP1dCycDf9RUbPHO+9d40ToFU4N3AqCbNCiU +E1PDJbMzEtKv7eWjWm8tBZ3Id3mJdaYlkDyFt1VedeQlLumndNHSTPFBv5Bmgoc RtDjO9YYee9r0A== X-ME-Sender: X-Sasl-enc: BIgqxv8Vy9XtozHjNML6VaWE5bQBTwcmn3t6GhPN7gHT 1496086341 Received: from [192.168.1.2] (75-172-126-41.tukw.qwest.net [75.172.126.41]) by mail.messagingengine.com (Postfix) with ESMTPA id 6860C2444C; Mon, 29 May 2017 15:32:21 -0400 (EDT) Subject: Re: Lost my tablespace To: tel medola Cc: pgsql-sql@postgresql.org References: <2a418dab-d17f-9d3a-0ac4-53678c1ce16f@aklaver.com> <97bd2743-46c3-32c4-7b3f-62def38aea65@aklaver.com> <32bb9df2-3b4d-95cb-1f82-8da675536a9b@aklaver.com> From: Adrian Klaver Message-ID: Date: Mon, 29 May 2017 12:32:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org On 05/29/2017 12:05 PM, tel medola wrote: > 1) In the below you are saying that you used that template to try to > recreate the original tables, correct? > > /No.I have not done anything yet to try to retrieve the information, > even though they are there. I just can not redo the links, even with the > inherit command already executed./ > > It seems you are doing something, that is what I am trying figure out. > What INHERIT command? > > /I did it, I'm not doing it./ > /After I returned the copy, I did nothing else. That "new" I said, I had The copy being the file system drive backups of each tablespace? > done before. But it's only "new" that I can get with the SELECT, the > others, not./ Then the below from your original post means?: "Is there any way Postgres redo the link with the child tables ?? I already ran the command to rewrite inheritance, but the size of the tables continues with 8192." > / > / > /When I run the \ d + command the involved tables are not shown. Not > even the one I can access via Select (only those that are in the public > schema are shown) > / You will either need to set the search_path to all the schemas involved, see example at bottom of page below: https://www.postgresql.org/docs/9.6/static/sql-set.html or schema.qualify the table name passed to \d+: \d+ some_schema.table_name > > But none of this was actually done when you tried to recover the tables. > > /When I returned the backup (drive copy, not pg_dump), I realized that > the information was not being found. I did not change anything else at > the database and sent the email to the community./ > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql