Skip site navigation (1) Skip section navigation (2)

Re: CVS checkout source code for different branches

From: M Z <jm80008(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, alvherre(at)commandprompt(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CVS checkout source code for different branches
Date: 2010-02-10 03:35:33
Message-ID: e824728e1002091935y26284792s8fae5ef2cfd4ac0f@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Final, I tried:

$ cvs -z3 -d :pserver:anoncvs:password(at)anoncvs(dot)postgresql(dot)org:/projects/cvsroot
co -r REL8_3_STABLE -P pgsql

Checked file configure.in. Around line 20, there is line:
 AC_INIT([PostgreSQL], [8.3.9], [pgsql-bugs(at)postgresql(dot)org])

Not sure that indicates version 8.3.9?

But still, is there a testing/developing version for 8.3? I remember Alvaro
made a patch to contrib/xml2/xpath.c. What is that version? and How can get
this version? Is there a way I can list all branches / versions in CVS
server?


*******************************************************************************
Index: contrib/xml2/xpath.c
==============================
=====================================
RCS file: /home/alvherre/Code/cvs/pgsql/contrib/xml2/xpath.c,v
retrieving revision 1.16.2.1
diff -c -p -r1.16.2.1 xpath.c
*** contrib/xml2/xpath.c        26 Mar 2008 01:19:11 -0000      1.16.2.1
--- contrib/xml2/xpath.c        27 Jan 2010 15:30:56 -0000
*************** xpath_table(PG_FUNCTION_ARGS)
*** 793,798 ****
--- 793,801 ----
  */
       pgxml_parser_init();

+       PG_TRY();
+       {
+
       /* For each row i.e. document returned from SPI */
       for (i = 0; i < proc; i++)
       {
*************** xpath_table(PG_FUNCTION_ARGS)
*** 929,934 ****
--- 932,944 ----
               if (xmldoc)
                       pfree(xmldoc);
       }
+       }
+       PG_CATCH();
+       {
+               xmlCleanupParser();
+               PG_RE_THROW();
+       }
+       PG_END_TRY();

       xmlCleanupParser();
 /* Needed to flag completeness in 7.3.1. 7.4 defines it as a no-op. */
*******************************************************************************

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-02-10 03:37:52
Subject: Re: Some belated patch review for "Buffers" explain analyze patch
Previous:From: Takahiro ItagakiDate: 2010-02-10 02:56:54
Subject: TRUNCATE+COPY optimization and --jobs=1 in pg_restore

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group