| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Freezing without write I/O |
| Date: | 2013-05-30 21:06:11 |
| Message-ID: | 20130530210611.GC4715@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 30, 2013 at 04:33:50PM +0300, Heikki Linnakangas wrote:
> This would also be the first step in allowing the clog to grow
> larger than 2 billion transactions, eliminating the need for
> anti-wraparound freezing altogether. You'd still want to truncate
> the clog eventually, but it would be nice to not be pressed against
> the wall with "run vacuum freeze now, or the system will shut down".
Keep in mind that autovacuum_freeze_max_age is 200M to allow faster clog
truncation. Does this help that?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2013-05-31 00:19:58 | Re: Behavior of a pg_trgm index for 2 (or < 3) character LIKE queries |
| Previous Message | Andres Freund | 2013-05-30 20:07:09 | Re: Vacuum, Freeze and Analyze: the big picture |