| From: | "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
| Cc: | "Rudolf van der Leeden" <vanderleeden(at)logicunited(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postgres 8.3 archive_command |
| Date: | 2007-11-22 09:34:52 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57902913758@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I don't think that should even be a TODO item --- it seems far more
> likely to provide a foot-gun than useful capability.
On further reflection I think that initdb time is probably sufficient.
Do you think that would be a reasonable TODO ?
> Whether 16MB is still a reasonable default segment size is worth
> questioning, though I don't think that increasing it is an
open-and-shut
> proposition. Larger segments mean more overhead in configurations
that
> force frequent segment switches, for instance.
Yes, imho there is no one size fits all (if there were, it would
probably be
between 32 and 64 Mb).
But there are installations where even 16Mb is too much e.g. for an
embedded device.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-11-22 09:50:48 | Re: 8.3devel slower than 8.2 under read-only load |
| Previous Message | Simon Riggs | 2007-11-22 09:29:46 | Re: 8.3devel slower than 8.2 under read-only load |