From sacadmin Mon Jan  7 08:58:56 2008
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m07GwuV2012618;
	Mon, 7 Jan 2008 08:58:56 -0800 (PST)
Received: (from jg97986@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m07GwuJZ012614;
	Mon, 7 Jan 2008 11:58:56 -0500 (EST)
Date: Mon, 7 Jan 2008 11:58:56 -0500 (EST)
From: James Gates <jg97986@sac.sfbay.sun.com>
Message-Id: <200801071658.m07GwuJZ012614@sac.sfbay.sun.com>
To: LSARC-record@sac.sfbay.sun.com
Cc: bjorn.munch@sun.com
Subject: EOF of PostgreSQL 8.1 in Solaris [LSARC/2008/005 FastTrack timeout 01/15/2008]
Status: RO
Content-Length: 568


Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 EOF of PostgreSQL 8.1 in Solaris
    1.2. Name of Document Author/Supplier:
	 Author:  Bjorn Munch
    1.3  Date of This Document:
	07 January, 2008
4. Technical Description
    See the case directory for more detail

6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open


From james.gates@sun.com Mon Jan  7 09:36:27 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m07HaQSR013564
	for <LSARC-ext@sac.sfbay.sun.com>; Mon, 7 Jan 2008 09:36:27 -0800 (PST)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m07HaQ26032402
	for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 7 Jan 2008 10:36:26 -0700 (MST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0JUA00K01BKQK300@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com
 (ORCPT lsarc-ext@sun.com); Mon, 07 Jan 2008 10:36:26 -0700 (MST)
Received: from dm-uk-01.uk.sun.com ([129.156.101.115])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0JUA00GGXBKOSE30@brm-avmta-1.central.sun.com> for
 lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon,
 07 Jan 2008 10:36:25 -0700 (MST)
Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208])
	by dm-uk-01.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2)
 with ESMTP id m07HaO8C009269; Mon, 07 Jan 2008 17:36:24 +0000 (GMT)
Received: from [192.168.1.100] (vpn-129-150-65-94.East.Sun.COM [129.150.65.94])
	by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0)
 with ESMTP id m07Ha3EL018572; Mon, 07 Jan 2008 17:36:12 +0000 (GMT)
Date: Mon, 07 Jan 2008 12:35:35 -0500
From: James Gates <james.gates@sun.com>
Subject: LSARC 2008/005 - EOF of PostgreSQL 8.1 in Solaris
To: lsarc-ext@sun.com
Cc: Bjorn Munch <Bjorn.Munch@sun.com>
Message-id: <478262E7.3040804@sun.com>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_EoT4eL8DkOsT15xaS6Apbg)"
X-Accept-Language: en-us, en
X-PMX-Version: 5.2.0.264296
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509
Status: RO
Content-Length: 8428

This is a multi-part message in MIME format.

--Boundary_(ID_EoT4eL8DkOsT15xaS6Apbg)
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT

I am sponsoring this fast-track on behalf of Bjorn Munch. The timer 
expires 01/15/08. Attached is a copy of the proposal, which can also be 
found in the case directory.

--Boundary_(ID_EoT4eL8DkOsT15xaS6Apbg)
Content-type: text/plain; name=8.1eof__fast_track_proposal.txt
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=8.1eof__fast_track_proposal.txt

Template Version: @(#)onepager.txt 1.35 07/11/07 SMI
Copyright 2007 Sun Microsystems

1. Introduction
   1.1. Project/Component Working Name:
        EOF of PostgreSQL 8.1 in Solaris

   1.2. Name of Document Author/Supplier:
	Bjorn Munch

   1.3. Date of This Document:
	12/19/07
	
	1.3.1. Date this project was conceived:
		12/01/07

   1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:
		
            Database PAC

	1.4.2. The ARC(s) you expect to review your project:

            LSARC

	1.4.3. The Director/VP who is "Sponsoring" this project:

            Heidi.Bergh-Hoff@sun.com

	1.4.4. The name of your business unit:

            Software

   1.5. Email Aliases:
    	1.5.1. Responsible Manager: Yngve.Svendsen@sun.com
    	1.5.2. Responsible Engineer: Bjorn.Munch@sun.com
    	1.5.3. Marketing Manager: Rebecca.Hansen@sun.com
	1.5.4. Interest List: sun-postgres-pteam@sun.com

2. Project Summary
   2.1. Project Description:

        [In the following "8.1", "8.2" or "8.3" without qualification
        refer to the corresponding PostgreSQL version.]

	In the discussions for the ARC case for integrating PostgreSQL
	8.2 (LSARC/2006/655) it was suggested that if 8.3 became
	integrated before FCS of Solaris 11, we might EOF 8.1,
	provided an upgrade tool/solution is available.

        PostgreSQL 8.3 will soon ready to be integrated, a separate ARC
        has been filed for this (LSARC/2008/004)

        With the integration of 8.3, we will provide an upgrade
        solution.  The exact implementation details are not finalized,
        but it will come in a separate package which likely will
        include a few binaries from 8.1 and a script.  It may include
        separate solutions for upgrade to 8.2 and to 8.3.

   2.2. Risks and Assumptions:

        If Solaris 11 is shipped without 8.1, it would force customers
        still running this version to upgrade PostgreSQL immediately
        if they upgrade their O/S.  They might even decide not to
        upgrade because of this.  I have no idea how many customers
        this might affect though, and it's not a problem for those who
        are already running 8.2.

        There is also a risk that some other Sun products depend on
        8.1; we need to ensure that these are upgraded to at least 8.2.
        I have verified that no other packages in the SFWNV
        consilidation are listed as depending on any of the PostgreSQL
        8.1 packages.

3. Business Summary

   3.1. Problem Area:
	
        For the users, the mere existence of the 8.1 installation
        under the default /usr/bin path can cause problems if they
        really want to run a later version.  They may on occation run
        the 8.1 version of e.g. psql (the interactive SQL client) by
        mistake.  I have done this myself during testing.

        Also, since 8.1 is more "easily" available, some users
        starting up with PostgreSQL might pick that version instead of
        the latest, which is something we want to discourage.

   3.2. Market/Requester:
	
        This was recommended in the discussions around the ARC case for
        PostgreSQL 8.2 (LSARC/2006/655).

   3.3. Business Justification:

        We want to reduce the amount of resources needed to sustain
        8.1 in the future.  We also want to remove one source of
        potential inconvenience for users who want to run PostgreSQL
        8.2 or 8.3.

   3.4. Competitive Analysis:
	
        N/A

   3.5. Opportunity Window/Exposure:
	
        This needs to be done after 8.3 and an upgrade solution
        becomes available, or at the same time.

   3.6. How will you know when you are done?:
   	
        When 8.1 has been removed from the SFWNV consolidation.

4. Technical Description:
    4.1. Details:

         This project will remove the following packages:

         SUNWpostgr-contrib
         SUNWpostgr-devel
         SUNWpostgr-docs
         SUNWpostgr-jdbc
         SUNWpostgr-libs
         SUNWpostgr-pl
         SUNWpostgr-server
         SUNWpostgr-server-data
         SUNWpostgr-tcl

    4.2. Bug/RFE Number(s):
	
        N/A
    
    4.3. In Scope:

    4.4. Out of Scope:
    
    4.5. Interfaces:

         All interfaces provided by the packages listed in section 4.1
         will be deleted.  This includes among others, the following files:

        /etc/pgsql/psqlrc.sample
        /usr/bin/DBMirror.pl
        /usr/bin/clean_pending.pl
        /usr/bin/dbf2pg
        /usr/bin/ecpg
        /usr/bin/fti.pl
        /usr/bin/initdb
        /usr/bin/ipcclean
        /usr/bin/oid2name
        /usr/bin/pg_config
        /usr/bin/pg_controldata
        /usr/bin/pg_ctl
        /usr/bin/pg_resetxlog
        /usr/bin/pgbench
        /usr/bin/pltcl_delmod
        /usr/bin/pltcl_listmod
        /usr/bin/pltcl_loadmod
        /usr/bin/postgres
        /usr/bin/postmaster
        /usr/bin/vacuumlo
        /usr/include/pgsql/*
        /usr/share/java/postgresql.jar
        /usr/share/pgsql/*
        /var/lib/pgsql/*

        Also deleted are a number of files under /usr/lib,
        /usr/share/man, /usr/share/doc, /usr/share/locale etc. too
        numerous to list here.

    4.6. Doc Impact:

	There is one Sun produced document that accompanies PostgreSQL (a
	small installation & configuration guide), this will be updated
	to remove the reference to PostgreSQL 8.1.
    
    4.7. Admin/Config Impact:

        None.
    
    4.8. HA Impact:

        N/A
    
    4.9. I18N/L10N Impact:

        No.
    
    4.10. Packaging & Delivery:

        The packages listed in 4.1 will be deleted and will not be
        included with the first release of Solaris 11. However, note
        that they have been delivered with SXDE; I don't know if this
        will require us to go through the full EOF process.

        Users upgrading from Solaris 10 who are running a database
        under PostgreSQL 8.1 will have to use the upgrade solution we
        plan to include with the 8.3 integration.
 
    4.11. Security Impact:

        No impact.
    
    4.12. Dependencies:

        Depends on the integration of 8.3 and an upgrade solution from
        8.1 to 8.3 (or 8.2); this is being filed as a separate ARC case.

5. Reference Documents:

	All material associated with the original ARC case to integrate
	PostgreSQL 8.1 can be found at:
	http://sac.sfbay.sun.com/LSARC/2005/515/

        Material associated with the ARC case to integrate PostgreSQL
        8.2 can be found at:
	http://sac.sfbay.sun.com/LSARC/2006/655/

        Material associated with the ARC case to integrate PostgreSQL
        8.3 can be found at
        http://sac.sfbay.sun.com/LSARC/2008/004

	PostgreSQL 8.3 information can be found at:
	http://www.postgresql.org/

6. Resources and Schedule:
   6.1. Projected Availability:

        Has a logical depencency on availability of PostgreSQL 8.3 and
        the upgrade tool, probably January 2008.  Can be done
        immediately once this is integrated.

   6.2. Cost of Effort:

        Minimal; just removal of a component.

   6.3. Cost of Capital Resources:
	
        None.

   	6.4.1. Consolidation or Component Name:

		SFW

	6.4.3. Type of CPT Review and Approval expected:

		FastTrack

        6.4.4. Project Boundary Conditions:

		N/A

	6.4.5. Is this a necessary project for OEM agreements:

               No

	6.4.6. Notes:

	6.4.7. Target RTI Date/Release:

               ASAP after the community releases 8.3.

	6.4.8. Target Code Design Review Date:
	6.4.9. Update approval addition:

   6.5. ARC review type:

        FastTrack

   6.6. ARC Exposure:

        open

       6.6.1. Rationale:

              N/A

7. Prototype Availability:
   7.1. Prototype Availability:
	
        N/A

   7.2. Prototype Cost:
	
        N/A

--Boundary_(ID_EoT4eL8DkOsT15xaS6Apbg)--

