Re: BUG #4096: PG 8.3.1. confused about remaining disk space - Mailing list pgsql-bugs
From | J6M |
---|---|
Subject | Re: BUG #4096: PG 8.3.1. confused about remaining disk space |
Date | |
Msg-id | 003f01c898b9$f835b460$1500020a@eden.fr Whole thread Raw |
In response to | BUG #4096: PG 8.3.1. confused about remaining disk space ("" <j6m@adm.estp.fr>) |
Responses |
Re: BUG #4096: PG 8.3.1. confused about remaining disk space
Re: BUG #4096: PG 8.3.1. confused about remaining disk space Re: BUG #4096: PG 8.3.1. confused about remaining disk space |
List | pgsql-bugs |
OK. So why did this not occur when I was running 8.2.6 ? To avoid any ambiguity, here we go estp-intranet:~ # su - postgres postgres@estp-intranet:~> cd /var/lib/pgsql postgres@estp-intranet:~> cd data postgres@estp-intranet:~/data> ls base pg_hba.conf pg_multixact pg_twophase postgresql.conf global pg_ident.conf pg_subtrans PG_VERSION postmaster.opts pg_clog pg_log pg_tblspc pg_xlog postmaster.pid postgres@estp-intranet:~/data> cd pg_xlog postgres@estp-intranet:~/data/pg_xlog> ls 000000010000000F00000040 000000010000000F00000055 000000010000000F0000006A 000000010000000F00000041 000000010000000F00000056 000000010000000F0000006B 000000010000000F00000042 000000010000000F00000057 000000010000000F0000006C 000000010000000F00000043 000000010000000F00000058 000000010000000F0000006D 000000010000000F00000044 000000010000000F00000059 000000010000000F0000006E 000000010000000F00000045 000000010000000F0000005A 000000010000000F0000006F 000000010000000F00000046 000000010000000F0000005B 000000010000000F00000070 000000010000000F00000047 000000010000000F0000005C 000000010000000F00000071 000000010000000F00000048 000000010000000F0000005D 000000010000000F00000072 000000010000000F00000049 000000010000000F0000005E 000000010000000F00000073 000000010000000F0000004A 000000010000000F0000005F 000000010000000F00000074 000000010000000F0000004B 000000010000000F00000060 000000010000000F00000075 000000010000000F0000004C 000000010000000F00000061 000000010000000F00000076 000000010000000F0000004D 000000010000000F00000062 000000010000000F00000077 000000010000000F0000004E 000000010000000F00000063 000000010000000F00000078 000000010000000F0000004F 000000010000000F00000064 000000010000000F00000079 000000010000000F00000050 000000010000000F00000065 000000010000000F0000007A 000000010000000F00000051 000000010000000F00000066 000000010000000F0000007B 000000010000000F00000052 000000010000000F00000067 000000010000000F0000007C 000000010000000F00000053 000000010000000F00000068 000000010000000F0000007D 000000010000000F00000054 000000010000000F00000069 archive_status postgres@estp-intranet:~/data/pg_xlog> cp -p 000000010000000F000000* .. postgres@estp-intranet:~/data/pg_xlog> As you can see, there is no problem to create new files on the filesystem with user postgres. ----- Original Message ----- From: "Tom Lane" <tgl@sss.pgh.pa.us> To: <j6m@adm.estp.fr> Cc: <pgsql-bugs@postgresql.org> Sent: Monday, April 07, 2008 4:09 PM Subject: Re: [BUGS] BUG #4096: PG 8.3.1. confused about remaining disk space > "" <j6m@adm.estp.fr> writes: >> A lot of messages like these do appear wich tend to indicate PG 8.3.1 is >> confused. This set of SQL scripts used to run from PG 7.0.3 to PG 8.2.6 >> with >> no problem. > >> WARNING: could not create relation-cache initialization file >> "base/19693/pg_internal.init.29329": No space left on device > > This is just PG reporting what the kernel told it. If there's any > "confusion" it's at the kernel level. > > I agree with Zdenek's diagnosis of user quota problems ... > > regards, tom lane > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs
pgsql-bugs by date: