Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dFh6H-00033B-D8 for pgsql-sql@arkaria.postgresql.org; Tue, 30 May 2017 13:22:17 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dFh6G-0003Ci-Ig for pgsql-sql@arkaria.postgresql.org; Tue, 30 May 2017 13:22:16 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFh6D-00039c-V9 for pgsql-sql@postgresql.org; Tue, 30 May 2017 13:22:14 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dFh66-00019U-IH for pgsql-sql@postgresql.org; Tue, 30 May 2017 13:22:12 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D603420682; Tue, 30 May 2017 09:22:04 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 30 May 2017 09:22:04 -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=YbNeTHlDR6mJBDyBYC 9OwEPfMgTIUdYyT1KI2MW52BE=; b=o1NvoTA2OhP0H6A+SgNlAoR5Qklm7+t73S qD5PF0uwVZ8YprVxRLhOvX278qNNIGBWVN2H6S7CDfz4Hq94y2Et9LzsRa8SpxDg jgxnbvjPr6xl4mtMoQUW81lMiyokuWt/il39zuVrBxCIiHjm+UWBor02nhw2O7yD /x1IBSFJVXfom423wMHJ9jBCuOsXw/Us29S4lWPH51eJx+cmz71u0sK/zvQNvG6l 06bhxgxrn4jy6P7nrVgsw73bMtdwv5P1tfpjYYpH10OKuJfr2MV2EKstK2tlNk0j gSIk/wJkBaQPkmRfQ8u+O3BEBq5KBC3ZcsYSDrURNoXWLNJKpSOQ== 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=YbNeTHlDR6mJBDyBYC9OwEPfMgTIUdYyT1KI2MW52BE=; b=A/GLqW9l M30S47UUZjI5lHkSKl8Vj/WtAoYWWa+kSWZBkCQGFbUu59UKxYit1jSJc9f49gUt nGD8VYLH4BU5CFYStY3YlIQ+ioAIwJ3Gan3db16nEZZQD1behbTtO1Mnrf3uyvhn kGqUjlS8H2ZoV/8ynh5jOuYV+dkIBBDwpCN+4+c1CHL4XNVLtFxRitQybN/VXRNi 37E7Zvbj/5IXVmVkFHK3+Y1fI3C9hAQMTX1AAj2l3OififvLHO2+IJwIKMqWcI6y BfDCA7su8wbwdbsd2dKvjrbG2tPCY3+lbQi6MxwveAgr7J52tjq6eQirsc9+gJIF sshV0I6MV5DfQA== X-ME-Sender: X-Sasl-enc: y1cpO/5ixDgTq1+ubugvXNiTHxOcXsRXQ8T7+pofOhjl 1496150524 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 57C6C7E794; Tue, 30 May 2017 09:22:04 -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: Tue, 30 May 2017 06:22:03 -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: 8bit 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/30/2017 05:11 AM, tel medola wrote: > Sorry by delay.... > > > The copy being the file system drive backups of each tablespace? > / > / > /Yes/ > / > / > Then the below from your original post means?/ > / > /That despite recovering the backup, I can not access my data. So I > posted that I lost my tablespaces./ > > 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) So how did you get the below? > > / Esquema | Nome | Tipo | Dono | Tamanho | Descrição/ > /----------+-------------+--------+----------+------------+-----------/ > / 01052016 | repositorio | tabela | postgres | 8192 bytes |/ > / 05122016 | repositorio | tabela | postgres | 8192 bytes |/ > / 13042017 | repositorio | tabela | postgres | 491 GB |/ > / 22082016 | repositorio | tabela | postgres | 8192 bytes |/ > / 30122015 | repositorio | tabela | postgres | 8192 bytes |/ > What does: show search_path; return? Did you try my previous suggestions: 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 As examples: SET search_path TO 01052016, 05122016 , 13042017, 22082016, 30122015 public; or For a single object(table, view, sequence) in a schema: \d+ 01052016.repositorio For all in a schema: \d+ 01052016.* -- 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