vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am running a 7.4.3 postgreSQL database on RHEL 3. I have encountered two cases where tables have multiple key values, in violation of a primary key constraint. I discovered this after receiving SQL exceptions, where the primary key constraint was all of a sudden being enforced again. This may be associated with a vacuum/analyze being done on the table in question. Has anyone heard of such a problem with v 7.4? Thanks. Philip Politowicz Database Administrator Berbee Information Networks 5520 Research Park Drive Fitchburg, WI 53711 philip.politowicz@berbee.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |