Hi Jeff!
No, the process that seems to grow indefinitely is postgres process
created for each active connection. The app side is fine.
Altogether we have 50 tables, only two are in the 200 mb range, the rest
is <50mb. While we query one of the big tables constantly (once every
min) but each co
On Sat, Dec 7, 2013 at 1:10 AM, Eliott wrote:
> Dear Community,
>
> we've recently moved one of our production databases from a 8.3 based
> server to a 9.2 installation. Our usage patterns remained the same,
> however, we noticed that the swap space in the server started to decrease
> with time.
Hi,
can the VACUUM FREEZE be skipped if
a) txid_current < vacuum_freeze_min_age or if
b) txid_current < vacuum_freeze_table_age or if
c) txid_current < autovacuum_freeze_max_age and no manual VACUUM has
been done?
Or is the operation perhaps only necessary for tables matching
select n.nspnam
Dear Community,
we've recently moved one of our production databases from a 8.3 based
server to a 9.2 installation. Our usage patterns remained the same,
however, we noticed that the swap space in the server started to
decrease with time.
We have roughly 16 connections to this database in an
