Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dLs2x-0005NW-NT for pgsql-docs@arkaria.postgresql.org; Fri, 16 Jun 2017 14:16:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dLs2w-0001ar-Np for pgsql-docs@arkaria.postgresql.org; Fri, 16 Jun 2017 14:16:22 +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 1dLs2Z-0000vi-8d for pgsql-docs@postgresql.org; Fri, 16 Jun 2017 14:15:59 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dLs2W-0002bp-PV for pgsql-docs@postgresql.org; Fri, 16 Jun 2017 14:15:57 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 22704207B7; Fri, 16 Jun 2017 10:15:56 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 16 Jun 2017 10:15:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=XYe8QWxadepNehRUNzXGWH6QjVth9ixQIs2Td/yf/Lc=; b=Khbk7J9Z 6sAv9gEBtKCqShr9WYB6wXdcvMqruk0esEwOybtjW81vN7nKvuuiSU/EJD3V0/J9 vKfimMmCHvMUPgbOY2SBGqov4aJUv8fR+/DD7Nxt6ckvjiaxlAQww5oRKJNE0Ybm KkXC5B22lv5KjIkViKjRIPmHpeUOeVLYAzfeVtzqH6vP37Nk8GOlretwdHourj+e KXwHfGvOA64qU2Mw3CcOoZK4qB4Npi4lAs9SziskzakQ+SQPxtGjRORTm4ReGA2R +EOdwCOnFWRiLLztl0vJYS1ytCWYMAJhmbhx9ryiqGKM/iX1urrLekO1FGjJkT6D eu05fJ1YZ1hy7w== X-ME-Sender: X-Sasl-enc: Y90oCmut6IWVM8j3S1onY5jBP/NzdGFUNHG37/mw80QM 1497622555 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id DA14C24850; Fri, 16 Jun 2017 10:15:55 -0400 (EDT) Subject: Re: pg_restore man page (version 9.4) > -d/dbname clarification request To: Charles , pgsql-docs@postgresql.org References: <59edd1d1-ecde-3cf4-1ca5-b18a81573e98@2ndquadrant.com> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <06e8a969-ca83-453b-ed0e-d8e92384eecd@2ndquadrant.com> Date: Fri, 16 Jun 2017 10:15:55 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 6/16/17 01:09, Charles wrote: > The suggestion was based on how pg_restore behaved when used this way > (as user postgres on a Debian Jessie server): > > $ dropdb redmine_default > $ pg_restore --create --dbname=postgres > redmine_default-2017-06-11@18\:21\:06.sql If you are using the --create option, you get a different behavior. This is pretty explicitly described on the pg_restore man page under --describe. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs