I noticed postgresql would do vacuum to prevent wraparound of the transaction id, and I also tried to use vacuum freeze, I am not quite sure about freeze, but it seems postgresql will still vacuum the frezzed unchanged tables automatically.
My scenario is, I have a table with daily partitions, those partition table inherits the parent table, with date check. Each day there is tens of millions rows, and old partitions won't be updated, they may be treat as readonly table. Meanwhile, there is hot-stanby server, we treat it as a readonly db. when we query on that db, we often got version conflict error, even on the old partitions. Is there any way better to deal this? -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
