Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dgG0n-0001qL-Ue for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 19:54:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dgG0n-0002HS-H7 for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 19:54:25 +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 1dgG0n-0002H6-0E for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 19:54:25 +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 1dgG0k-0002v8-Db for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 19:54:23 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id DBFA520D28; Fri, 11 Aug 2017 15:54:21 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 11 Aug 2017 15:54:21 -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=WQgOK3AF253GXDnOBCjWXTTM8GnxvtOTHxOon+xlzI8=; b=oRYM5cRu FZdy4hmyENDRPFgDuelnAceK+Dnl88dHb7NtlvGu8tRTDjJeZGoph+j6ccEweJnW q0znrDyI2U/TKJFFa4SL+KugE0JzFeNaCL7vZlJNznMhl2oH2ilZDmhrbys0qupA t1iV7eWVV36bbXQrVR3qhUm7Zc1AyPmIuth8KAO+UnQT28XxuYZRX4aW45WRAsWn fUHtkYXYv251/h4/E48LcJ3z9/rQBFxf6vbnHgASO7Sbw+78+/r7iZ8s755x3kdd 1APKK21UG/9108m09dLiwFFvALB0RPeDAQDY8bKRXYLqMJwBA0wmUedtLqaGOnm4 Zj2kWX/d08wr3w== X-ME-Sender: X-Sasl-enc: 2v1d3aPXGBVpDGxjFhDJ5+3Hh9aOr9ipDlqyqO8ijhHP 1502481261 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 96D1B244B4; Fri, 11 Aug 2017 15:54:21 -0400 (EDT) Subject: Re: pg_restore -l documentation To: Jeff Janes , pgsql-docs@postgresql.org References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <53a31757-416f-250c-3690-a3bc799b7f46@2ndquadrant.com> Date: Fri, 11 Aug 2017 15:54:21 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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 8/3/17 15:56, Jeff Janes wrote: > The docs for the -l switch in pg_restore say: > > List the contents of the archive. > > this is weird, because everywhere else we use "table of contents" to > describe this, which makes it seem like just plain 'contents' should > mean the bulk table data. > > Attached patch changes it to say: > > List the table of contents of the archive. Committed, thanks! -- 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