Index: FAQ.html =================================================================== RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ.html,v retrieving revision 1.235 diff -c -r1.235 FAQ.html *** FAQ.html 16 Dec 2004 01:08:23 -0000 1.235 --- FAQ.html 17 Dec 2004 23:36:56 -0000 *************** *** 339,346 **** href= "http://techdocs.PostgreSQL.org/">http://techdocs.PostgreSQL.org/.

!

psql has some nice \d commands to show information about ! types, operators, functions, aggregates, etc.

Our web site contains even more documentation.

--- 339,347 ---- href= "http://techdocs.PostgreSQL.org/">http://techdocs.PostgreSQL.org/.

!

The command line client program psql has some \d commands to show ! information about types, operators, functions, aggregates, etc. - use \? to ! display the available commands.

Our web site contains even more documentation.

*************** *** 425,445 ****
Performance
!
PostgreSQL has performance similar to other commercial and ! open source databases. it is faster for some things, slower for others. In comparison to MySQL or leaner database systems, we are faster for multiple users, complex queries, and a read/write query load. MySQL is faster for simple SELECT queries done by a few users. Of course, MySQL does not have most of the features mentioned in the Features section above. We are built for reliability and features, and we continue to improve performance in every ! release. There is an interesting Web page comparing PostgreSQL to ! MySQL at ! http://openacs.org/philosophy/why-not-mysql.html Also, MySQL is ! is a company that distributes its products via open source, and requires ! a commercial license for close-source software, not an ! open source development community like PostgreSQL.
!
--- 426,440 ----
Performance
!
PostgreSQL's performance is comparable to other commercial and ! open source databases. It is faster for some things, slower for others. In comparison to MySQL or leaner database systems, we are faster for multiple users, complex queries, and a read/write query load. MySQL is faster for simple SELECT queries done by a few users. Of course, MySQL does not have most of the features mentioned in the Features section above. We are built for reliability and features, and we continue to improve performance in every ! release.

*************** *** 498,509 **** "contributions" item is solely to support the PostgreSQL project and does not fund any specific company. If you prefer, you can also send a check to the contact address.

-

Also, if you have a success story about PostgreSQL, please submit it to our advocacy site at http://advocacy.postgresql.org.

User Client Questions

--- 493,504 ---- "contributions" item is solely to support the PostgreSQL project and does not fund any specific company. If you prefer, you can also send a check to the contact address.

Also, if you have a success story about PostgreSQL, please submit it to our advocacy site at http://advocacy.postgresql.org.

+

User Client Questions

*************** *** 544,550 ****

Yes, there are several graphical interfaces to PostgreSQL available. These include PgAccess ! http://www.pgaccess.org), PgAdmin III (http://www.pgadmin.org, RHDB Admin (http://sources.redhat.com/rhdb/ ), TORA (http://www.globecom.net/tora/ --- 539,545 ----

Yes, there are several graphical interfaces to PostgreSQL available. These include PgAccess ! http://www.pgaccess.org), pgAdmin III (http://www.pgadmin.org, RHDB Admin (http://sources.redhat.com/rhdb/ ), TORA (http://www.globecom.net/tora/ *************** *** 674,682 **** kernel's limit on shared memory space. Each buffer is 8K and the default is 1000 buffers.

!

You can also use the sort_mem and work_mem options ! to increase the maximum amount of memory used by the backend processes ! for each temporary sort. The default is 1024 (i.e. 1MB).

You can also use the CLUSTER command to group data in tables to match an index. See the CLUSTER --- 669,677 ---- kernel's limit on shared memory space. Each buffer is 8K and the default is 1000 buffers.

!

You can also use the sort_mem (from PostgreSQL 8.0: work_mem) ! options to increase the maximum amount of memory used by the backend ! processes for each temporary sort. The default is 1024 (i.e. 1MB).

You can also use the CLUSTER command to group data in tables to match an index. See the CLUSTER *************** *** 1170,1183 **** execute("INSERT INTO person (name) VALUES ('Blaise Pascal')"); new_id = execute("SELECT currval('person_id_seq')"); ! ! Finally, you could use the OID returned from the INSERT statement to look up the default value, though this is probably the least portable approach, and the oid value will wrap around when it reaches 4 billion. ! In Perl, using DBI with Edmund Mergl's DBD::Pg module, the oid ! value is made available via $sth->{pg_oid_status} after ! $sth->execute().

4.15.3) Doesn't currval() lead to a race condition with other users?

--- 1165,1178 ---- execute("INSERT INTO person (name) VALUES ('Blaise Pascal')"); new_id = execute("SELECT currval('person_id_seq')"); ! !

Finally, you could use the OID returned from the INSERT statement to look up the default value, though this is probably the least portable approach, and the oid value will wrap around when it reaches 4 billion. ! In Perl, using DBI with the DBD::Pg module, the oid value is made ! available via $sth->{pg_oid_status} after ! $sth->execute().

4.15.3) Doesn't currval() lead to a race condition with other users?