On 26.06.2013 17:15, Tom Lane wrote:
Heikki Linnakangas writes:
We've discussed retrying short writes before, and IIRC Tom has argued
that it shouldn't be necessary when writing to disk. Nevertheless, I
think we should retry in XLogWrite(). It can write much bigger chunks
than most write() call
, 32 Maskit St., Herzliya 46733, Israel
Mobile: +972 54 6107703, Office: +972 9 9710239; Fax: +972 9 9710222
-Original Message-
From: Andres Freund [mailto:and...@2ndquadrant.com]
Sent: Wednesday, June 26, 2013 4:04 PM
To: Heikki Linnakangas
Cc: Greg Stark; Tom Lane; Jeff Davis; Yuri Lev
Heikki Linnakangas writes:
> We've discussed retrying short writes before, and IIRC Tom has argued
> that it shouldn't be necessary when writing to disk. Nevertheless, I
> think we should retry in XLogWrite(). It can write much bigger chunks
> than most write() calls, so there's more room for a
e; Jeff Davis; Yuri Levinsky; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Postgres crash? could not write to log file: No
spaceleft on device
On 2013-06-26 13:14:37 +0100, Greg Stark wrote:
> On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane wrote:
> > (Though if it is, it's not apparent wh
On 2013-06-26 15:40:08 +0300, Heikki Linnakangas wrote:
> On 26.06.2013 15:21, Andres Freund wrote:
> >On 2013-06-26 13:14:37 +0100, Greg Stark wrote:
> >>On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane wrote:
> >>> (Though if it is, it's not apparent why such
> >>>failures would only be manifesting o
On 26.06.2013 15:21, Andres Freund wrote:
On 2013-06-26 13:14:37 +0100, Greg Stark wrote:
On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane 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 o
On 2013-06-26 13:14:37 +0100, Greg Stark wrote:
> On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane 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 chun
On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane 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
Jeff Davis writes:
> On Tue, 2013-06-25 at 09:46 -0400, Tom Lane wrote:
>> That's definitely telling you it got ENOSPC from a write in
>> $PGDATA/pg_xlog.
> Either that, or write() wrote less than expected but did not set errno.
Good point. I wonder if he's using a filesystem that is capable of
On Tue, 2013-06-25 at 09:46 -0400, Tom Lane wrote:
> "Yuri Levinsky" writes:
> > PANIC: could not write to log file 81, segment 125 at offset 13959168,
> > length 1392640: No space left on device
>
> That's definitely telling you it got ENOSPC from a write in
> $PGDATA/pg_xlog.
Either that, or
bricklen writes:
> Assuming your stats_temp_directory is pg_stat_tmp, where is that directory
> located? Under $PGDATA?
> What is the path to $PGDATA?
> If your stats_temp_directory is located on a small partition, that could be
> a problem
> Where is your pg_xlog dir located?
The given error mes
On Tue, Jun 25, 2013 at 9:43 AM, Yuri Levinsky wrote:
> I inspected my config file and didn't see any destination that isn't
> /data/postgres. Have I perform any specific setting to limit it into
> /data/postgres?
Execute from psql:
show stats_temp_directory
stats_temp_directory
+972 9 9710222
From: Lou Picciano [mailto:loupicci...@comcast.net]
Sent: Tuesday, June 25, 2013 5:34 PM
To: Yuri Levinsky
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Postgres crash? could not write to log file: No spaceleft
on device
Yuri, You're sure the pg xlogs are going wher
3:00 - (UTC)
Subject: [BUGS] Postgres crash? could not write to log file: No space left on
device
Dear All, I have the following issue on Sun Solaris 10. PostgreSQL version is
9.2.3. The wall logging is minimal and no archiving. The DB restarted several
time, the box is up for last 23
+972 9 9710222
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Tuesday, June 25, 2013 4:47 PM
To: Yuri Levinsky
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Postgres crash? could not write to log file: No
spaceleft on device
"Yuri Levinsky" writes:
> I hav
"Yuri Levinsky" writes:
> I have the following issue on Sun Solaris 10. PostgreSQL version is
> 9.2.3. The wall logging is minimal and no archiving. The DB restarted
> several time, the box is up for last 23 days. The PostgreSQL
> installation and files under /data/postgres that is half empty. Is
Dear All,
I have the following issue on Sun Solaris 10. PostgreSQL version is
9.2.3. The wall logging is minimal and no archiving. The DB restarted
several time, the box is up for last 23 days. The PostgreSQL
installation and files under /data/postgres that is half empty. Is it
some other destinat
hi,
we had a server crash today - had to fsck and postgres is corrupted now
if i try a pg_dump i get:
inetmain:/tmp/tests$ pg_dump -c -v -d factline1 > /tmp/factline1_20011025_144800.sql
-- saving database definition
getDatabase(): SELECT failed. Explanation from backend: 'ERROR: pg_atoi:
er
18 matches
Mail list logo
