rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses

rule system at that time was described in [ston87a]. The rationale and architecture of the storage manager were detailed in [ston87b]. POSTGRES has undergone several major releases since then. The first by IBM3) picked up the code and commercialized it. In late 1992, POSTGRES became the primary data manager for the Sequoia 2000 scientific computing project4. The size of the external user community nearly entirely determined by the OVER clause. The rows considered by a window function are those of the “virtual table” produced by the query's FROM clause as filtered by its WHERE, GROUP BY, and HAVING clauses