Thank you very much for all your inputs. I believe "analyze" is the one
I should use .
Quoth [EMAIL PROTECTED] (Emi Lu):
no. the suggestion was that a VACUUM is not needed, but that an
ANALYZE might be.
Thank you gnari for your answer. But I am a bit confused about not
running vacuu
Quoth [EMAIL PROTECTED] (Emi Lu):
>> no. the suggestion was that a VACUUM is not needed, but that an
>> ANALYZE might be.
>
> Thank you gnari for your answer. But I am a bit confused about not
> running vacuum but only "analyze". Can I seperate these two
> operations? I guess "vacuum analyze" do bo
On fös, 2006-02-17 at 12:06 -0500, Emi Lu wrote:
> In another way, whenever we "delete/truncate and then insert" data into
> a table, it is better to "vacuum anaylze"?
>
> ...
> >>
> >>So, your suggestion is that after the population of table A, the query
> >>planner should be abl
On Fri, 2006-02-17 at 11:06, Emi Lu wrote:
> In another way, whenever we "delete/truncate and then insert" data into
> a table, it is better to "vacuum anaylze"?
>
>
>
>
> >>>You shouldn't need a VACUUM if you haven't yet done any updates or
> >>>deletes sinc
In another way, whenever we "delete/truncate and then insert" data into
a table, it is better to "vacuum anaylze"?
You shouldn't need a VACUUM if you haven't yet done any updates or
deletes since the TRUNCATE. An ANALYZE seems like a good idea, though.
(You could get away without
On fim, 2006-02-16 at 16:24 -0500, Emi Lu wrote:
> >>In another way, whenever we "delete/truncate and then insert" data into
> >>a table, it is better to "vacuum anaylze"?
> >>
> >>
> >You shouldn't need a VACUUM if you haven't yet done any updates or
> >deletes since the TRUNCATE. An ANALYZE
In another way, whenever we "delete/truncate and then insert" data into
a table, it is better to "vacuum anaylze"?
You shouldn't need a VACUUM if you haven't yet done any updates or
deletes since the TRUNCATE. An ANALYZE seems like a good idea, though.
(You could get away without ANALYZE
Emi Lu <[EMAIL PROTECTED]> writes:
> In another way, whenever we "delete/truncate and then insert" data into
> a table, it is better to "vacuum anaylze"?
You shouldn't need a VACUUM if you haven't yet done any updates or
deletes since the TRUNCATE. An ANALYZE seems like a good idea, though.
(You
On fim, 2006-02-16 at 09:12 -0500, Emi Lu wrote:
> Hello,
>
> We have a daily cronjob and in the cronjob we do:
> 1. truncate one table A
> 2. insert into table A
> 3. do comparision table A and table B and update table B accordingly
>
> The doc says "VACUUM ANALYZE command for the affec
Hello,
We have a daily cronjob and in the cronjob we do:
1. truncate one table A
2. insert into table A
3. do comparision table A and table B and update table B accordingly
The doc says "VACUUM ANALYZE command for the affected table. This will
update the system catalogs with the results o
10 matches
Mail list logo
