Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iT2DC-0003yv-Th for pgsql-bugs@arkaria.postgresql.org; Fri, 08 Nov 2019 11:13:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iT2DA-0000h6-Sm for pgsql-bugs@arkaria.postgresql.org; Fri, 08 Nov 2019 11:13:52 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iT2DA-0000gz-EP for pgsql-bugs@lists.postgresql.org; Fri, 08 Nov 2019 11:13:52 +0000 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iT2D6-0005y4-BP for pgsql-bugs@lists.postgresql.org; Fri, 08 Nov 2019 11:13:51 +0000 Received: by mail-wm1-x342.google.com with SMTP id q70so5761944wme.1 for ; Fri, 08 Nov 2019 03:13:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=sid4h6Qi5XGK1JPxTW36jRF1Pvd0uuJyOqQe8tLvTXU=; b=rQBeELQgll4vbJBRl8/q8iEQXZlFgiop5c9DG3F7UQoJpD62fjzyxUgjrlR4VyPJne EVFf5IK2yNKH6AFJszljbgplrnMkDBLEFO/GtGKygHD5xuBr/rhILhdjlfKF0gntxfY2 I6qtt6zD3KW4ivSBRCld9cyylItaKDO5aTgYpzC/6CahboDMsEJbP4MIpSFlJiwJYeOH 0WnCIPxeMU/9yP6ao2QnHTJ/dV0c8lCOD8+vwWZk/cfzvajC4uAuMJR3TXn26G/igHRK uxay4set8uQKqOLK/cXerey99wj9iDIKzdNGotDbtG69ARAgyLeugNfneh7rkJbuqd7C twPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=sid4h6Qi5XGK1JPxTW36jRF1Pvd0uuJyOqQe8tLvTXU=; b=RPlgGJzstZWmTLolnGQDawyLKJ1CKIiJUGuipBvZZlbDsKBCx0f1NBXEK05qbvjAV8 n5TDmt3LvecYSg84dAZYXaXjwSQe+1h0BbYefSbeLEyEOUCL/a8cndzqIg4aiKG86XvR y9z8lp8APLxtQ0N/rXigD4hEXX+mxjuBGcJ9YXJ3DZEAkm+etZHGknwn/lRYC1jh/49J 5urkQsRUOTV+wqHdTvjMYVw+UDI3kwCHRo/Mby/dwEb92fEKiuMIihXPyevhuIc91ILD yq4bk1nJQ6I5O9Y8j+J2UO0KZON103MQC8n4gD/I3QKfFxsbs2x6FFiCkSfdUMwDSwzS R1FA== X-Gm-Message-State: APjAAAUJfecCs1yy7uCCS2nAzNcjiUEz+86lu4XGJh8Kk50PfKqiLmZi DXEPknU1s6jfyGMDjYD17u6IcA== X-Google-Smtp-Source: APXvYqwbO8komhkS4GjstYL2X9XNhlL1o/r1KHdaXsxuDLQhR4PNYAKKhP78mYp0iSW9++ntIy0sQQ== X-Received: by 2002:a1c:6a09:: with SMTP id f9mr7693245wmc.15.1573211626923; Fri, 08 Nov 2019 03:13:46 -0800 (PST) Received: from localhost ([217.8.174.100]) by smtp.gmail.com with ESMTPSA id b8sm5539069wrt.39.2019.11.08.03.13.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 08 Nov 2019 03:13:44 -0800 (PST) Date: Fri, 8 Nov 2019 12:13:39 +0100 From: Tomas Vondra To: 270246512@qq.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16101: tables in the DB is not available after pg_restore Message-ID: <20191108111339.xlopjkbwfhxfvwt3@development> References: <16101-5a569e5aac6aa84e@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16101-5a569e5aac6aa84e@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Nov 08, 2019 at 07:37:24AM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16101 >Logged by: zeng >Email address: 270246512@qq.com >PostgreSQL version: 10.10 >Operating system: suse >Description: > >hi, >I have one question about pg_restore tool, tables in the DB is not available >after restore. Even if the user is still the owner of table after restore. >Steps: >1. Create one database and the owner is user1. And create table and pop >the data with user1 >2. Use pg_dump tool to backup one database with superuser postgres. >3. Use pg_restore tool to restore the database with the parameter –clean >and supper user. >4. Connect the db with user1 and found the user does not select table as >below. > cdb=> \dt >Did not find any relations. > A wild guess - the objects are in a schema that is not listed in search_path. If that's not the case, you'll have to give us more details, and perhaps a reproducer so that we can look more closely. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services