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

RE: [HACKERS] vacuum process size

From: "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, t-ishii(at)sra(dot)co(dot)jp
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: RE: [HACKERS] vacuum process size
Date: 1999-08-25 13:56:30
Message-ID: 1BF7C7482189D211B03F00805F8527F70ED134@S-NATH-EXCH2 (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
The reason for the tag as to be able to return to the 6.5 release source
code.  It's production code, and should be accessible at least for the next
couple of months.

Was a tag created for 6.5.1?  The object is to be able to check out any
particular release, bugs and all, whenever we feel like it.


>> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> > Just for a confirmation: I see REL6_5_PATCHES and REL6_5 Tag in the
>> > CVS respository. I thought that REL6_5_PATCHES is the Tag 
>> for the 6.5
>> > statble tree and would eventually become 6.5.2. If so, what is the
>> > REL6_5 Tag? Or I totally miss the point?
>> Right, REL6_5_PATCHES is the 6.5.* branch.  REL6_5 is just a tag ---
>> that is, it's effectively a frozen snapshot of the 6.5 release,
>> not an evolvable branch.
>> I am not sure if Marc intends to continue this naming convention
>> in future, or if it was just a mistake to create REL6_5 as a tag
>> not a branch.  I don't see a whole lot of use for the frozen tag
>> myself...
>> 			regards, tom lane
>> ************


pgsql-hackers by date

Next:From: The Hermit HackerDate: 1999-08-25 14:05:54
Subject: Re: [HACKERS] vacuum process size
Previous:From: Tatsuo IshiiDate: 1999-08-25 13:50:39
Subject: Re: [HACKERS] vacuum process size

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