Received: from makus.postgresql.org ([98.129.198.125])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1T0FoQ-0008VF-Fb
	for pgsql-docs@postgresql.org; Sat, 11 Aug 2012 17:49:22 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1T0FoP-0002Aq-JG
	for pgsql-docs@postgresql.org; Sat, 11 Aug 2012 17:49:21 +0000
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q7BHnK1s009179;
	Sat, 11 Aug 2012 13:49:20 -0400 (EDT)
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Janes <jeff.janes@gmail.com>
cc: pgsql-docs@postgresql.org
Subject: Re: Documentation cross reference from copy to \copy
In-reply-to: 
 <CAMkU=1wYJhQT0rrDYmGXJNEQgMG9SxXDG1rFRDuhnYxLYDnskw@mail.gmail.com>
References: 
 <CAMkU=1wYJhQT0rrDYmGXJNEQgMG9SxXDG1rFRDuhnYxLYDnskw@mail.gmail.com>
Comments: In-reply-to Jeff Janes <jeff.janes@gmail.com>
	message dated "Fri, 10 Aug 2012 09:24:06 -0700"
Date: Sat, 11 Aug 2012 13:49:20 -0400
Message-ID: <9178.1344707360@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201208/8
X-Sequence-Number: 7401

Jeff Janes <jeff.janes@gmail.com> writes:
> Where the SQL COPY command warns us not to confuse it with \copy, a
> link to \copy would be useful.  The attached patch implements that,
> but I'm not sure it does so in the preferred way.

It seems reasonable from here.  I thought at first that it might break
the man-page output, but AFAICT there is no effect on that.

			regards, tom lane