Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id EC285133798E for ; Thu, 30 Sep 2010 04:00:40 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 90363-04 for ; Thu, 30 Sep 2010 07:00:33 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id 57EF91335B36 for ; Thu, 30 Sep 2010 04:00:32 -0300 (ADT) Received: from [192.168.1.6] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0LwmRY-1OhZj51Tlg-016SPU; Thu, 30 Sep 2010 09:00:24 +0200 Message-ID: <4CA43586.7050503@2ndquadrant.com> Date: Thu, 30 Sep 2010 03:00:22 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Peter Eisentraut CC: Tom Lane , Satoshi Nagayasu , Robert Haas , pgsql-docs Subject: Re: ECPG - Some errno definitions don't match to the manual References: <4C4847D0.9030001@gmail.com> <4C602E9D.40501@gmail.com> <4C60C7A9.10307@gmail.com> <4C634586.7090908@gmail.com> <1285502270.1601.1.camel@vanquo.pezone.net> <4CA11FF7.1090403@gmail.com> <4CA13D11.7050905@gmail.com> <4CA1458F.9030707@2ndquadrant.com> <17708.1285656381@sss.pgh.pa.us> <1285676832.20420.2.camel@vanquo.pezone.net> In-Reply-To: <1285676832.20420.2.camel@vanquo.pezone.net> Content-Type: multipart/alternative; boundary="------------080107060901020301000901" X-Provags-ID: V02:K0:bKrNUlC1g21cgs2cYDqDuoVXHsdWI+DjuBXBWJKntg/ 3roQ3tkYff2Yo7tD/SU/BkxaHcGjK5bLHSVzCF5ev5e/Ssv/OV 3NhQZ+GcN7NYv/kvAvgc72BxD3hhCoH96ZKgm0KkI4IKC5DMMx 2WVb7CP9UhdLA/ka4WkHixYPaTj/uCqh3xA6QZQexiW/cClxUp xEeMmvPyCvFsWV72dS4tdxWRZsmuW1YKcCijHYT1Oc= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.899 tagged_above=-5 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201009/147 X-Sequence-Number: 6137 This is a multi-part message in MIME format. --------------080107060901020301000901 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Peter Eisentraut wrote: > On tis, 2010-09-28 at 02:46 -0400, Tom Lane wrote: > >> Greg Smith writes: >> >>> I just made a pass through the wiki cleaning up all of the outdated CVS >>> related stuff I knew of there that this page was pointing to. It's a >>> sequential group of 9 changes to revert if we're forsaken and somehow >>> this conversion stops. Main thing left with obsolete info is >>> http://developer.postgresql.org/pgdocs/postgres/cvs.html >>> >> Hrm, that page shouldn't even exist anymore. Peter? >> > > I've changed the doc build to use rsync so that orphaned files get > deleted. > That one is fixed. Doesn't look like the incoming path from the main postgresql.org page is completely sorted out yet though now that I check that too. If people start at http://www.postgresql.org/developer/coding and click "Information about the Source Code Repository", they'll head to http://www.postgresql.org/docs/current/static/git.html - good so far - but clicking on "Up" from there goes to the 9.0 http://www.postgresql.org/docs/current/static/cvs.html still, suggesting the official repo is the CVS one. Not sure if that is just cached stuff on the static pages that Peter's rsync change will clear eventually too, or if that's a final piece that needs a backport to fix. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us Author, "PostgreSQL 9.0 High Performance" Pre-ordering at: https://www.packtpub.com/postgresql-9-0-high-performance/book --------------080107060901020301000901 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Peter Eisentraut wrote: 
On tis, 2010-09-28 at 02:46 -0400, Tom Lane wrote:
  
Greg Smith <greg@2ndquadrant.com> writes:
    
I just made a pass through the wiki cleaning up all of the outdated CVS 
related stuff I knew of there that this page was pointing to.  It's a 
sequential group of 9 changes to revert if we're forsaken and somehow 
this conversion stops.  Main thing left with obsolete info is 
http://developer.postgresql.org/pgdocs/postgres/cvs.html
      
Hrm, that page shouldn't even exist anymore.  Peter?
    

I've changed the doc build to use rsync so that orphaned files get
deleted.

That one is fixed.  Doesn't look like the incoming path from the main postgresql.org page is completely sorted out yet though now that I check that too.  If people start at http://www.postgresql.org/developer/coding and click "Information about the Source Code Repository", they'll head to http://www.postgresql.org/docs/current/static/git.html - good so far - but clicking on "Up" from there goes to the 9.0 http://www.postgresql.org/docs/current/static/cvs.html still, suggesting the official repo is the CVS one.

Not sure if that is just cached stuff on the static pages that Peter's rsync change will clear eventually too, or if that's a final piece that needs a backport to fix.

-- 
Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services and Support  www.2ndQuadrant.us
Author, "PostgreSQL 9.0 High Performance"    Pre-ordering at:
https://www.packtpub.com/postgresql-9-0-high-performance/book
--------------080107060901020301000901--