Attached is a proposal for a fast-track ARC case for pgBouncer.
Please comment..

--Magne


Template Version: @(#)onepager.txt 1.31 07/08/08 SMI

This information is Copyright 2007 Sun Microsystems

1. Introduction
    1.1. Project/Component Working Name:
          pgBouncer - Provide PostgreSQL connection pooling
          for OpenSolaris

    1.2. Name of Document Author/Supplier:
          Magne Mahre

    1.3. Date of This Document:
          2007-12-06

    1.4. Name of Major Document Customer(s)/Consumer(s):
         1.4.1. The Community you expect to review your project:
         Databases

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

    1.5. Email Aliases:
         1.5.2. Responsible Engineer:
         Magne Mahre <magne.mahre at sun.com>

         1.5.4. Interest List:
         databases-discuss at sun.com

2. Project Summary
    2.1. Project Description:
         pgBouncer is the most popular connection pool mechanism for
         PostgreSQL.  This project aims to provide pgBouncer as a part
         of the OpenSolaris distribution(s).


3. Business Summary
    3.2. Market/Requester:
         pgBouncer is a pri. 1 requirement from the Databases P-Team.

4. Technical Description:
     4.1. Details:
          pgBouncer is a part of the PostgreSQL Global Development
          Team effort, with the bulk of the code supplied by Skype.
          The product implements a connection pooling front-end for
          PostgreSQL databases allowing muliple client to share a
          set of database connections for efficiency purposes.

          Opening, keeping and closing database connections has
          a cost in time and cpu/disk resources.  To lower this
          cost, pgBouncer opens and holds a number of database
          connections that can be used by clients to execute
          transaction.

          When the client needs to execute a database transaction,
          it will direct the query to pgBouncer, which in turn
          will forward the query to the database using one of the
          set of pre-opened connections.  When the transaction
          completes, the client will release the connection
          back to pgBouncer, and it will be available for the
          next client.

          Connection pooling is a feature required by most
          "Web 2.0" installations, and also by other users.


          http://pgfoundry.org/projects/pgbouncer/


     4.5. Interfaces:

         /usr/bin/pgbouncer
         /etc/pgbouncer     [D]
         /etc/pgbouncer/pgbouncer.ini
         /usr/share/man/man1/pgbouncer.1
         /usr/share/man/man5/pgbouncer.5
         /usr/share/doc/pgbouncer [D]
         /usr/share/doc/pgbouncer/* (various text files)


     4.12. Dependencies:
         PostgreSQL v.8.x


6. Resources and Schedule:
    6.1. Projected Availability:
         Q3FY08

    6.4. Product Approval Committee requested information:
         6.4.1. Consolidation or Component Name:
         SFWNV

    6.5. ARC review type:
         FastTrack



Reply via email to