Ok, thanks.
I was also planning on manually running vacuum, reindex and analyze on the main DB after removing the data from the main DB after archiving. Does that sound necessary and reasonable ?
On Tue, Nov 24, 2020 at 10:15 AM Adrian Klaver <adrian.klaver@xxxxxxxxxxx> wrote:
On 11/24/20 6:36 AM, David Gauthier wrote:
> Hi:
>
> 11.3 on linux
>
> I've come up with a plan to archive data from my main DB which involves
> creating other DBs on the same server. But even though there will be
> zero activity on the archive DBs in terms of insert/update/delete, and
> almost no activity in terms of select, I'm still worried that the mere
> existence of these other DBs will steal resources away from the instance
> and degrade performance in my main DB. So my question is whether or not
> that worry is valid or not.
The primary resource I see they taking is storage. If you have adequate
space so that the primary and archive databases can grow into it then I
don't see a problem on that score. There will also be some additional
overhead for the automatic VACUUM and ANALYZE operations. Since the
archive databases are quiescent that will be on the order of monitoring
not really processing.
>
> Thanks in Advance for any help !
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
