I chose to rebuild the entire table as I didn't really have the
necessary time to investigate what went wrong beyond of what I already did.
I have tried various scenarios for reproducing the problem but I failed
in doing that. The fact is that there were a large number of PGAdmin
crashes in the
<[EMAIL PROTECTED]> writes:
> Hmm... maybe this will help: in the same function (i.e. transaction), I am
> also doing an update on the same table, using suid as update key, that is:
> update migratek.mt set sdate = smth where suid = s.suid;
Do the rows in the output to the second query I sent (th
Tom, Gregory,
Thank you for your replies. I will try reindexing the table but I am not
very sure that will make any difference.
The reason is that when I built the table, I was building it making sure
there are unique values that get trown into it, in addition to the
constraint defined in the tabl
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Razvan Costea-Barlutiu" <[EMAIL PROTECTED]> writes:
>> This has way too many ramifications for me to follow so I do appreciate some
>> guidance.
> What do the outputs of these queries say?
It would also be interesting to know whether REINDEXing the tab
"Razvan Costea-Barlutiu" <[EMAIL PROTECTED]> writes:
> Hello.
>
> Facts:
> 1. System: Win2003
> 2. Postgres 8.2
Is that just 8.2 or 8.2.x? Which x?
> This has way too many ramifications for me to follow so I do appreciate some
> guidance.
What do the outputs of these queries say?
select count(
