Changeset 3903
- Timestamp:
- Nov 1, 2007, 2:46:31 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/src/docbook/admindoc/installation_upgrade.xml
r3871 r3903 707 707 <listitem> 708 708 <para> 709 PostgreSQL 8. 0seems to be working very well with709 PostgreSQL 8.2 seems to be working very well with 710 710 BASE and Hibernate. Download and install PostgreSQL, 711 711 available from … … 716 716 comment out the settings for MySQL. 717 717 </para> 718 719 <note> 720 <para> 721 Postgres versions prior to 8.2 have a non-optimal solution 722 for locking rows in certain situations. This may cause two 723 seemingly independent transactions to lock if they just 724 reference a common database row. This may happen, for example, 725 when importing raw data that have references to the same 726 reporters. The problem has been solved in Postgres 8.2. 727 </para> 728 </note> 729 718 730 </listitem> 719 731 </varlistentry>
Note: See TracChangeset
for help on using the changeset viewer.