• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Tools

Sorted by:
Try your query at:
Semantic Scholar Scholar Academic
Google Bing DBLP
Results 11 - 20 of 39,718
Next 10 →

Table B-1. SQL Key Words Key Word PostgreSQL SQL 99 SQL 92

in PostgreSQL 7.1 User's Guide
by The Postgresql Global, Postgresql User's Guide

Table 6.1: Selected data types in Informix and PostgreSQL

in Reviewers:
by Jutta Horstmann, Prof Dr, Herbert Weber, Dipl Phys, Jürgen Oheim, Dr. Mattis Neiling 2005

Table 6.2 provides an overview on the Informix tools currently used at the WZB and commands and their PostgreSQL counterparts.

in Reviewers:
by Jutta Horstmann, Prof Dr, Herbert Weber, Dipl Phys, Jürgen Oheim, Dr. Mattis Neiling 2005

TABLE II THE POSTGRESQL8.2 CONFIGURATION PARAMETERS AND THEIR VALUES USED. EACH PAGE SIZE IS 8KB.

in SCRAP: A Statistical Approach for Creating a Database Query Workload Based on Performance Bottlenecks
by James Skarie, Biplob K. Debnath, David J. Lilja, Mohamed F. Mokbel

Table 1. Size of tables in MB with 500k rows and 5 present values per row as stored in our PostgreSQL pro- totype.

in Extending RDBMSs to support sparse datasets using an interpreted attribute storage format
by Jennifer L. Beckmann, Alan Halverson, Rajasekar Krishnamurthy, Jeffrey F. Naughton 2006
"... In PAGE 7: ... The sparsity of the synthetic data used in our experiments never exceeds that of the real world CNET data, therefore the synthetic data is not artificially sparse. Table1 lists the size of the respective storage schemes for the tables as stored in PostgreSQL. The table illustrates how the storage schemes scale with the number of possi- ble attributes.... ..."
Cited by 6

Table 1: Results of various machine learning classifiers on classifying release and work stages in PostgreSQL aggregate MRs (10% classify, 90% train)

in Software Process Extraction and Identification
by Abram Hindle, Michael W. Godfrey, Richard C. Holt

Table 2: Overall transaction throughput comparison between the MVCC version of Phoenix and PostgreSQL under the TPC-C benchmark in terms of number of transactions executed per sec- ond. W is the number of warehouses.

in Design, Implementation, and Evaluation of A Repairable Database Management System
by unknown authors
"... In PAGE 9: ... Each user submits this transaction mix to the database server over a period of two hours. Table2 shows the comparison in the transaction throughput between Phoenix-MVCC and PostgreSQL, in terms of number of transactions processed in one minute, which is the standard throughput metric for TPC-C bench- marks. The TPC-C specification models a warehousing business and allows scaling the database size by increas- ing the number of warehouses (W).... ..."

Table 2.2: Installation management database functions. These functions should not be used in multi-row queries because no rollback mechanism is available. This limitation is mostly due to lack of exception handling in PostgreSQL.

in Data and Computation Modeling for Scientific Problem Solving Environments
by Alex A. Verstak, Alex A. Verstak 2002
Cited by 2

TABLE II BUGS FOUND BY THE REDUNDANT ASSIGNMENT CHECKER IN LINUX VERSION 2.4.5-AC8, OPENBSD 3.2, AND POSTGRESQL 7.2.

in Using Redundancies to Find Errors
by Yichen Xie , Dawson Engler

TABLE III BUGS FOUND BY THE DEAD CODE CHECKER ON LINUX VERSION 2.4.5-AC8, OPENBSD 3.2, AND POSTGRESQL 7.2.

in Using Redundancies to Find Errors
by Yichen Xie , Dawson Engler
Next 10 →
Results 11 - 20 of 39,718
Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University