Dirk Lutzebaeck ([EMAIL PROTECTED]) wrote:
> I have observed the same problems and posted this a while ago. I'm
> *not* using large objects. On my side this seems to happen when making
> excessive update/inserts in conjunction with unique indexes.
Well, I have both unique and non-unique indexes, depending on the
table. So it's probably the same problem, or very closely related.
Did you see this with 6.4.2, or some other version? I may try the 6.5
beta, but I really do want to get rid of the large objects before
attempting a database upgrade, and I probably won't be able to get rid
of the large objects until next week. I just hope I don't need to drop
PostgreSQL altogether and go with some other database. :-(
