Tuning one DB while playing with other

[NoRiver]

I'm trying to setup two DB's 1 curent and main from which HUD could also take data.
Now main DB is just imported without any tuning, even without cash table. It will take 20 houres for full tunnig aproximately. On other hand i want play right now with current DB.
So my questions are :
1. Is it possible to run tunning - vaccuum, analyze on main DB while I will be playing with current DB and HUD will be active. PT can't alow it but I can run vaccuum, analyze, maybe cluster from PGadmin or other tools?
2. Is there any difference in commands an it's order beetween built-in in PT and native.
3. How much it can affect perfomance.
4. Maybe it's even possible to build cash table in background with sql command on separate DB

How that's config working at all. Is 2 cash table used by HUD. How about perfomance?

[kraada]

VACUUM and ANALYZE do not take very much time by themselves - even on a new database with quite a lot of data you're still only talking a handful of minutes; it's definitely worth doing. You could it in the background from PostgreSQL directly if you really wanted but for 5 minutes of your time it doesn't seem worth not waiting and just getting it done properly. There's no difference between VACUUM and ANALYZE as done in PT3 or via PostgreSQL directly.

The cache cannot be built outside of PT3 and cannot be built while PT3 is running on the database in question. It may take considerable time to run, but the performance boost will be considerable. You can try running PT3 without an up to date cache but it will be much, much slower and the HUD could take quite a while to appear.

Once you have a cache that's up to date, using two databases in the HUD won't be any problem.