| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, Yuri Levinsky <yuril(at)celltick(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Postgres crash? could not write to log file: No space left on device |
| Date: | 2013-06-26 12:21:05 |
| Message-ID: | 20130626122105.GA6660@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2013-06-26 13:14:37 +0100, Greg Stark wrote:
> On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > (Though if it is, it's not apparent why such
> > failures would only be manifesting on the pg_xlog files and not for
> > anything else.)
>
> Well data files are only ever written to in 8k chunks. Maybe these
> errors are only occuring on >8k xlog records such as records with
> multiple full page images. I'm not sure how much we write for other
> types of files but they won't be written to as frequently as xlog or
> data files and might not cause errors that are as noticeable.
We only write xlog in XLOG_BLCKSZ units - which is 8kb by default as
well...
Yuri, have you compiled postgres with nonstandard configure or
pg_config_manual.h settings?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gabriel.ct | 2013-06-26 12:21:22 | BUG #8255: encoding latin1 |
| Previous Message | Greg Stark | 2013-06-26 12:14:37 | Re: Postgres crash? could not write to log file: No space left on device |