| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: freezing tuples ( was: Why is vacuum_freeze_min_age 100m? ) |
| Date: | 2009-08-16 12:14:16 |
| Message-ID: | 1250424856.26280.0.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On lör, 2009-08-15 at 16:55 -0700, Jeff Davis wrote:
> Similarly, you could call vacuum_freeze_min_age "the maximum age a
> tuple
> can be before a vacuum will freeze it".
Heh, you could also call max_connections the "minimum number of
connections before the server will refuse new connection attempts".
It's not easy ... ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-08-16 12:35:03 | docs for random function |
| Previous Message | Jan Otto | 2009-08-16 11:27:11 | drop tablespace error: invalid argument |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Max Reymond | 2009-08-16 13:02:15 | Re: Less expensive proprietary or Open source ETL tools |
| Previous Message | simon@2ndquadrant.com | 2009-08-16 09:10:28 | Re: Scalability in postgres |