Hello,
I first wrote, by mistake, to the sql mailing list. But here is my e-mail:
I wrote a script to make sure all tables are vacuumed and analyzed every
evening. This works very well.
I save in a table the start and end time of a vacuum/analyze. This way I
can measure what tables take a long ti
Bert wrote:
> I wrote a script to make sure all tables are vacuumed and analyzed every
> evening. This works very
> well.
Autovacuum doesn't do the job for you?
That would save you from worries like the ones you have.
> Does anyone has an idea why in this case the vacuum/analyze takes almost as
> autovacuum is still enabled, but we want to avoid autovacuum to hit right
in the day / when the etl is
> working. So that's why we want to shedule it by hand, before autovacuum
starts.
I see.
> Is it a good idea to exclude those tables then? And run only vacuum /
analyze on the child tables, an
I'm doing the same thing. In my case, the vacuum part on parent is very
quick while analyzing takes a bit longer since it runs rough analyzes
all children tables. You can see the behavior by "analyze verbose".
Maybe the bigger part of your vacuum/analyze is on analyze so that you
are seeing thi
Yes, at the moment that is still the case.
We are migrating from db2 to postgres, and are still in progress of
migrating our ETL tool. So there isn't much moment in those tables at the
moment.
We got big big problems with db2 auto runstats (sort of auto analyze)
kicking in at random moments, that
*Hi Bert,*
**
*Vaccum analyze operation would be a time consuming activity when it
operates on partitioned table in parent and child relationship by using a
manual vaccum option. When vaccum operation is performed the total
vacuum/analyze time would be total time on completion of the said actvity
o
Hello,
I can see why that would be a good practice if you do a daily load, but the
goal is to have a 'live' dwh. with updated statistics every so-many-hours.
Thank you for the information anyway. I guess I will ask more questions
here when time passes. And I'll try to share some knowlegde too! :)
Hi Bert,
Yes, ETL process needs to load the data every day into datawarehouse
database from OLTP database and there would be no DML operations executing
on DWH DB which is mainly used for analyzing the data and getting the
reports for making business decisions. After every data load process,
stati
On Thu, Jan 24, 2013 at 7:43 AM, Prashanth Ranjalkar <
prashant.ranjal...@gmail.com> wrote:
> be no DML operations executing on DWH DB which is mainly used for
> analyzing the data and getting the reports for making business decisions.
> After every data load process, statistices should be updated
