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
"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
Tom,
There are no any space quota on user postgres. It always happens on
different log files. When I am creating huge dummy file in same FS -
nothing wrong.
P.S. I am getting same error when I am using pg_dump in tar format. I
don't know if there is some relation between 2 issues. The reason of t
Yuri, You're sure the pg xlogs are going where you expect them to? Have you
fine-tooth-combed your conf file for log file-related settings? Log files may
well be directed to fs other than /data/postgres (as is common in our
environments, e.g.)
Do a $ df -h on the various FSes involved...
Are y
Hi,
I did it before rising the question: no ZFS, Solaris 10 64 bit, I am personally
created manually 2G files – no limitations, the logs location is correct and
individual files timestamps are up today. It's not always happening – 1-3
times a day. I inspected my config file and didn't see any
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
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, 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
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
