Ok, tnx !!
On 21 Jun 2005, at 18:54, John A Meinel wrote:
Yves Vindevogel wrote:
I only add records, and most of the values are "random"
Except the columns for dates,
I doubt that you would need to recreate indexes. That really only needs
to be done in pathological cases, most of which hav
Yves Vindevogel wrote:
I only add records, and most of the values are "random"
Except the columns for dates,
I doubt that you would need to recreate indexes. That really only needs
to be done in pathological cases, most of which have been fixed in the
latest postgres.
If you are only ins
I only add records, and most of the values are "random"
Except the columns for dates,
On 21 Jun 2005, at 17:49, John A Meinel wrote:
Yves Vindevogel wrote:
And, after let's say a week, would that index still be optimal or
would it be a good idea to drop it in the weekend and recreate it.
Yves Vindevogel wrote:
And, after let's say a week, would that index still be optimal or
would it be a good idea to drop it in the weekend and recreate it.
It depends a little bit on the postgres version you are using. If you
are only ever adding to the table, and you are not updating it or
d
And, after let's say a week, would that index still be optimal or would it be a good idea to drop it in the weekend and recreate it.
On 21 Jun 2005, at 17:22, John A Meinel wrote:
Yves Vindevogel wrote:
Hi,
I have another question regarding indexes.
I have a table with a lot of indexes on it.
Yves Vindevogel wrote:
Hi,
I have another question regarding indexes.
I have a table with a lot of indexes on it. Those are needed to
perform my searches.
Once a day, a bunch of records is inserted in my table.
Say, my table has 1.000.000 records and I add 10.000 records (1% new)
What would
Hi,
I have another question regarding indexes.
I have a table with a lot of indexes on it. Those are needed to perform my searches.
Once a day, a bunch of records is inserted in my table.
Say, my table has 1.000.000 records and I add 10.000 records (1% new)
What would be faster.
1) Dropping m
