Greg Wooledge ([EMAIL PROTECTED]) wrote:
> I recreated the tables without large objects on Friday. (I created two
> tables to hold 4000-byte chunks and keep them straight, and I wrote
> frontend perl code which chops the files into pieces or reconstructs
> them. I'm not q
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.
And later:
> Only with 6.5beta so far, not with
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,
Greg Wooledge ([EMAIL PROTECTED]) wrote:
> PostgreSQL 6.4.2, compiled and installed on AIX 4.3.2 (a PowerPC
> system).
> Everything was going fairly well until this morning.
It's even worse today. *None* of the updates succeeded this morning.
I was able to do queries, but the da
PostgreSQL 6.4.2, compiled and installed on AIX 4.3.2 (a PowerPC
system).
Everything was going fairly well until this morning. I noticed a
problem when I tried to do a routine query on my database this morning --
it's a front-page CGI that I've run dozens of times over the last few
days. There
