Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dLuKj-00060j-Er for pgsql-docs@arkaria.postgresql.org; Fri, 16 Jun 2017 16:42:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dLuKh-0002Ke-V2 for pgsql-docs@arkaria.postgresql.org; Fri, 16 Jun 2017 16:42:51 +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 1dLuKf-0002J6-MZ for pgsql-docs@postgresql.org; Fri, 16 Jun 2017 16:42:49 +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 1dLuKY-0005K5-RE for pgsql-docs@postgresql.org; Fri, 16 Jun 2017 16:42:48 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B6BB820121; Fri, 16 Jun 2017 12:42:41 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 16 Jun 2017 12:42:41 -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=yxiw7YP/dxIKHZxvGB78B7YbvANSxswTZp0fOzsjPVM=; b=bGmA9tFz HqeJQ4P+I7sRwrDrXanmow6zqPt4vcvn8hGPJjC52K59IJl7IMxM2hPEMgebx7MX fcnZQ5rlc8hG9oWkWDVEadYR2Y3aAQFA/lvHglVJUMQ9DWyiHGpwxT9NxRQzVx9s wmkZ1uSK7CIRMBDaPqFysvU7kXIBHN8o4BT7sW7OYylUw8gEeJIf6z/2cL11oaJD 3HXFoAhYnxS4+pgP57rWtfDWUaFa18wl75M+0VH46OByScNPYmY7XmaqVeI2S5f2 Pxr+qVdQ0m/vJK9vvcgd5d7D8xPv42pulOBDNs+p+72a/xTHP/ktlTskalmbLrSq liIDfly0t7dqiw== X-ME-Sender: X-Sasl-enc: 4aT6SkY0y3tmFkmH/bjyEjI3QKDAvU8BMj5IF5YBLTSF 1497631361 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 723F424850; Fri, 16 Jun 2017 12:42:41 -0400 (EDT) Subject: Re: pg_restore man page (version 9.4) > -d/dbname clarification request From: Peter Eisentraut To: Charles , pgsql-docs@postgresql.org References: <59edd1d1-ecde-3cf4-1ca5-b18a81573e98@2ndquadrant.com> <06e8a969-ca83-453b-ed0e-d8e92384eecd@2ndquadrant.com> Organization: 2ndQuadrant Message-ID: <2c97b83b-0c0d-8a8a-e729-5911da5406cc@2ndquadrant.com> Date: Fri, 16 Jun 2017 12:42:41 -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: <06e8a969-ca83-453b-ed0e-d8e92384eecd@2ndquadrant.com> 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 10:15, Peter Eisentraut wrote: > 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. I mean under --create. -- 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