pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
No Space left on Device
9+ messages / 8 participants
[nested] [flat]

* No Space left on Device
@ 2002-12-31 17:27  Jose <javalis@sympatico.ca>
  0 siblings, 2 replies; 9+ messages in thread

From: Jose @ 2002-12-31 17:27 UTC (permalink / raw)
  To: pgsql-admin

Hi there, I'm Jose From Canada,

  I'm working with PostgreSQL 7.2 on Linux Red hat 7.3 and when I try to
create an object in the database, using PGAdmin or psql, I get this error.

  create index pp_key on pp (p1) ;

  Error: -2147467259  can not create object : no space left on device.


  But if I check the available space on disk from linux I have a lot, more
than 4 GB and the table pp is empty.


  Any clues ??? what should I check ???

Thanks in advance





^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: No Space left on Device
@ 2003-01-02 00:27  John Burski <jburski@cloudnet.com>
  parent: Jose <javalis@sympatico.ca>
  1 sibling, 0 replies; 9+ messages in thread

From: John Burski @ 2003-01-02 00:27 UTC (permalink / raw)
  To: Jose <javalis@sympatico.ca>; +Cc: pgsql-admin

It has been my experience that the message indicates the partition that 
contains your PostgreSQL data is full.

Try the "df -h" command to determine if this might be the case.

Jose wrote:

>Hi there, I'm Jose From Canada,
>
>  I'm working with PostgreSQL 7.2 on Linux Red hat 7.3 and when I try to
>create an object in the database, using PGAdmin or psql, I get this error.
>
>  create index pp_key on pp (p1) ;
>
>  Error: -2147467259  can not create object : no space left on device.
>
>
>  But if I check the available space on disk from linux I have a lot, more
>than 4 GB and the table pp is empty.
>
>
>  Any clues ??? what should I check ???
>
>Thanks in advance
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>.
>
>  
>

-- 
John Burski

@HOME S.I.M.U. (Well, sometimes I am :)  )

... and still searching for the cheese!






^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: No Space left on Device
@ 2003-01-02 05:26  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Jose <javalis@sympatico.ca>
  1 sibling, 0 replies; 9+ messages in thread

From: Tom Lane @ 2003-01-02 05:26 UTC (permalink / raw)
  To: Jose <javalis@sympatico.ca>; +Cc: pgsql-admin

"Jose" <javalis@sympatico.ca> writes:
>   I'm working with PostgreSQL 7.2 on Linux Red hat 7.3 and when I try to
> create an object in the database, using PGAdmin or psql, I get this error.
>   create index pp_key on pp (p1) ;
>   Error: -2147467259  can not create object : no space left on device.

This error is not coming from Postgres: the string 'can not create
object' does not appear anywhere in the PG source code.  Nor does the
format of the message match anything in Postgres -- we don't use error
numbers.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* No space left on device
@ 2004-02-11 15:12  Veera Sivakumar <vsivakumar@rm.com>
  0 siblings, 3 replies; 9+ messages in thread

From: Veera Sivakumar @ 2004-02-11 15:12 UTC (permalink / raw)
  To: pgsql-admin

Hi
I am using Postgres Database  version 7.3.1.
I am getting following error when I am starting postmaster. I could not be able to start the postmaster.
Pl help me 

Regard
Shiva Kumar



LOG:  database system was shut down at 2005-02-03 05:35:03 GMTST
LOG:  checkpoint record is at 0/B9C0C0
LOG:  redo record is at 0/B9C0C0; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 11687; next oid: 34453
LOG:  database system is ready
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
WARNING:  ROLLBACK: no transaction in progress
PANIC:  ZeroFill failed to write /usr/share/postgresql/data/pg_xlog/xlogtemp.3452: No space left on device
Stack trace:
Frame     Function  Args
0022CA78  7C4F1B1B  (00000000, 00000001, 00000000, 5C676F6C)
0022CAE8  61073C3B  (00000000, 0022CB20, 0022C000, 61079DD9)
0022CB38  6107109A  (00000D7C, 00000006, 0022CB98, 61073331)
0022CB88  610712B2  (00000D7C, 00000006, 0022CBD8, 610717EA)
0022CB98  6107115C  (00000006, 00000006, 00231378, 0022CDD8)
0022CBD8  610717EA  (610C0370, 0022CC30, 0000006B, 0022CDD8)
0022CDC8  0059BEF2  (00000016, 00427680, 0022EE00, 005C2490)
0022F618  004278B1  (00000000, 00000001, 0022F637, 00000001)
0022F638  00427D2C  (00000000, 00C02598, 00000000, 00002000)
0022F6B8  0042C015  (00000000, 00000000, 00000000, 00000003)
0022F6E8  00430F46  (00000005, 0022F7C0, 00000040, 77F89964)
0022F9D8  0050E975  (00000003, 005FAE00, 00000000, 0022F8A4)
0022FA58  0050BFB5  (00000002, 00000001, 00000000, 0A0467A0)
0022FEB8  0050B327  (00000004, 0A0403E0, 7C4E91AA, 00000001)
0022FEF0  004DBB2E  (00000004, 615E0644, 0A040328, 0022FF24)
0022FF40  61007418  (610C3A28, FFFFFFFE, 000003D4, 610C394C)
End of stack trace (more stack frames may be present)LOG:  server process (pid 3452) was terminated by signal 6
LOG:  terminating any other active server processes
WARNING:  Message from PostgreSQL backend:
	The Postmaster has informed me that some other backend
	died abnormally and possibly corrupted shared memory.
	I have rolled back the current transaction and am
	going to terminate your database system connection and exit.
	Please reconnect to the database system and repeat your query.
WARNING:  Message from PostgreSQL backend:
	The Postmaster has informed me that some other backend
	died abnormally and possibly corrupted shared memory.
	I have rolled back the current transaction and am
	going to terminate your database system connection and exit.
	Please reconnect to the database system and repeat your query.
LOG:  all server processes terminated; reinitializing shared memory and semaphores
IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not enough core

This error usually means that PostgreSQL's request for a shared
memory segment exceeded available memory or swap space.
To reduce the request size (currently 1441792 bytes), reduce
PostgreSQL's shared_buffers parameter (currently 64) and/or
its max_connections parameter (currently 32).

The PostgreSQL Administrator's Guide contains more information about
shared memory configuration.

LOG:  database system was interrupted at 2004-02-09 12:22:12 GMTST
LOG:  checkpoint record is at 0/C02558
LOG:  redo record is at 0/C02558; undo record is at 0/0; shutdown FALSE
LOG:  next transaction id: 11988; next oid: 42645
LOG:  database system was not properly shut down; automatic recovery in progress
LOG:  ReadRecord: record with zero length at 0/C02598
LOG:  redo is not required
0022AAD8  7C4F1B1B  (00000000LOG:  startup process (pid 4608) was terminated by signal 6
LOG:  aborting startup due to startup process failure
LOG:  database system was shut down at 2004-02-09 12:26:17 GMTST
LOG:  checkpoint record is at 0/C02598
LOG:  redo record is at 0/C02598; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 11988; next oid: 42645
PANIC:  ZeroFill failed to write /usr/share/postgresql/data/pg_xlog/xlogtemp.2816: No space left on device
Stack trace:
Frame     Function  Args
0022AAD8  7C4F1B1B  (00000000, 00000001, 00000000, 5C676F6C)
0022AB48  61073C3B  (00000000, 0022AB80, 0022A000, 61079DD9)
0022AB98  6107109A  (00000B00, 00000006, 0022ABF8, 61073331)
0022ABE8  610712B2  (00000B00, 00000006, 0022AC38, 610717EA)
0022ABF8  6107115C  (00000006, 00000006, 00000000, 0022AE38)
0022AC38  610717EA  (610C0370, 0022AC90, 0000006B, 0022AE38)
0022AE28  0059BEF2  (00000016, 00427680, 0022CE60, 005C2490)
0022D678  004278B1  (00000000, 00000001, 0022D697, 00000001)
0022D698  00427D2C  (00000000, 00C025D8, 00001A28, 0000A695)
0022F738  0042B0BC  (00000001, 005FADF0, 00000000, 00000003)
0022F768  00430EE4  (00000005, 0022F840, 00000040, 6107F684)
0022FA58  0050E975  (00000002, 00000001, 00000000, 0A0467A0)
0022FEB8  0050B31D  (00000004, 0A0403E0, 7C4E91AA, 00000001)
0022FEF0  004DBB2E  (00000004, 615E0644, 0A040328, 0022FF24)
0022FF40  61007418  (610C3A28, FFFFFFFE, 000003D4, 610C394C)
0022FF90  610076FD  (00000000, 00000000, FFFFFFFF, 80430D04)
End of stack trace (more stack frames may be present)LOG:  startup process (pid 2816) was terminated by signal 6
LOG:  aborting startup due to startup process failure
LOG:  database system was shut down at 2004-02-09 12:26:17 GMTST
LOG:  checkpoint record is at 0/C02598
LOG:  redo record is at 0/C02598; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 11988; next oid: 42645
FATAL:  The database system is starting up
FATAL:  The database system is starting up
PANIC:  ZeroFill failed to write /usr/share/postgresql/data/pg_xlog/xlogtemp.2704: No space left on device
Stack trace:
Frame     Function  Args
0022AAD8  7C4F1B1B  (00000000, 00000001, 00000000, 5C676F6C)
0022AB48  61073C3B  (00000000, 0022AB80, 0022A000, 61079DD9)
0022AB98  6107109A  (00000A90, 00000006, 0022ABF8, 61073331)
0022ABE8  610712B2  (00000A90, 00000006, 0022AC38, 610717EA)
0022ABF8  6107115C  (00000006, 00000006, 00000000, 0022AE38)
0022AC38  610717EA  (610C0370, 0022AC90, 0000006B, 0022AE38)
0022AE28  0059BEF2  (00000016, 00427680, 0022CE60, 005C2490)
0022D678  004278B1  (00000000, 00000001, 0022D697, 00000001)
0022D698  00427D2C  (00000000, 00C025D8, 00001A28, 0000A695)
0022F738  0042B0BC  (00000001, 005FADF0, 00000000, 00000003)
0022F768  00430EE4  (00000005, 0022F840, 00000040, 6107F684)
0022FA58  0050E975  (00000002, 00000001, 00000000, 0A0467A0)
0022FEB8  0050B31D  (00000004, 0A0403E0, 7C4E91AA, 00000001)
0022FEF0  004DBB2E  (00000004, 615E0644, 0A040328, 0022FF24)
0022FF40  61007418  (610C3A28, FFFFFFFE, 000003D4, 610C394C)
0022FF90  610076FD  (00000000, 00000000, FFFFFFFF, 80430D04)
End of stack trace (more stack frames may be present)LOG:  startup process (pid 2704) was terminated by signal 6
LOG:  aborting startup due to startup process failure
LOG:  database system was shut down at 2004-02-09 12:26:17 GMTST
LOG:  checkpoint record is at 0/C02598
LOG:  redo record is at 0/C02598; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 11988; next oid: 42645
PANIC:  ZeroFill failed to write /usr/share/postgresql/data/pg_xlog/xlogtemp.2056: No space left on device
Stack trace:
Frame     Function  Args
0022AAD8  7C4F1B1B  (00000000, 00000001, 00000000, 5C676F6C)
0022AB48  61073C3B  (00000000, 0022AB80, 0022A000, 61079DD9)
0022AB98  6107109A  (00000808, 00000006, 0022ABF8, 61073331)
0022ABE8  610712B2  (00000808, 00000006, 0022AC38, 610717EA)
0022ABF8  6107115C  (00000006, 00000006, 00000000, 0022AE38)
0022AC38  610717EA  (610C0370, 0022AC90, 0000006B, 0022AE38)
0022AE28  0059BEF2  (00000016, 00427680, 0022CE60, 005C2490)
0022D678  004278B1  (00000000, 00000001, 0022D697, 00000001)
0022D698  00427D2C  (00000000, 00C025D8, 00001A28, 0000A695)
0022F738  0042B0BC  (00000001, 005FADF0, 00000000, 00000003)
0022F768  00430EE4  (00000005, 0022F840, 00000040, 6107F684)
0022FA58  0050E975  (00000002, 00000001, 00000000, 0A0467A0)
0022FEB8  0050B31D  (00000004, 0A0403E0, 7C4E91AA, 00000001)
0022FEF0  004DBB2E  (00000004, 615E0644, 0A040328, 0022FF24)
0022FF40  61007418  (610C3A28, FFFFFFFE, 000003D4, 610C394C)
0022FF90  610076FD  (00000000, 00000000, FFFFFFFF, 80430D04)
End of stack trace (more stack frames may be present)LOG:  startup process (pid 2056) was terminated by signal 6
LOG:  aborting startup due to startup process failure
LOG:  database system was shut down at 2004-02-09 12:26:17 GMTST
LOG:  checkpoint record is at 0/C02598
LOG:  redo record is at 0/C02598; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 11988; next oid: 42645
PANIC:  ZeroFill failed to write /usr/share/postgresql/data/pg_xlog/xlogtemp.2056: No space left on device
Stack trace:
Frame     Function  Args
0022AAD8  7C4F1B1B  (00000000, 00000001, 00000000, 5C676F6C)
0022AB48  61073C3B  (00000000, 0022AB80, 0022A000, 61079DD9)
0022AB98  6107109A  (00000808, 00000006, 0022ABF8, 61073331)
0022ABE8  610712B2  (00000808, 00000006, 0022AC38, 610717EA)
0022ABF8  6107115C  (00000006, 00000006, 00000000, 0022AE38)
0022AC38  610717EA  (610C0370, 0022AC90, 0000006B, 0022AE38)
0022AE28  0059BEF2  (00000016, 00427680, 0022CE60, 005C2490)
0022D678  004278B1  (00000000, 00000001, 0022D697, 00000001)
0022D698  00427D2C  (00000000, 00C025D8, 00001A28, 0000A695)
0022F738  0042B0BC  (00000001, 005FADF0, 00000000, 00000003)
0022F768  00430EE4  (00000005, 0022F840, 00000040, 6107F684)
0022FA58  0050E975  (00000002, 00000001, 00000000, 0A0467A0)
0022FEB8  0050B31D  (00000004, 0A0403E0, 7C4E91AA, 00000001)
0022FEF0  004DBB2E  (00000004, 615E0644, 0A040328, 0022FF24)
0022FF40  61007418  (610C3A28, FFFFFFFE, 000003D4, 610C394C)
0022FF90  610076FD  (00000000, 00000000, FFFFFFFF, 80430D04)
End of stack trace (more stack frames may be present)LOG:  startup process (pid 2056) was terminated by signal 6
LOG:  aborting startup due to startup process failure
LOG:  database system was shut down at 2004-02-09 12:26:17 GMTST
LOG:  checkpoint record is at 0/C02598
LOG:  redo record is at 0/C02598; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 11988; next oid: 42645
PANIC:  ZeroFill failed to write /usr/share/postgresql/data/pg_xlog/xlogtemp.4504: No space left on device
Stack trace:
Frame     Function  Args
0022AAD8  7C4F1B1B  (00000000, 00000001, 00000000, 5C676F6C)
0022AB48  61073C3B  (00000000, 0022AB80, 0022A000, 61079DD9)
0022AB98  6107109A  (00001198, 00000006, 0022ABF8, 61073331)
0022ABE8  610712B2  (00001198, 00000006, 0022AC38, 610717EA)
0022ABF8  6107115C  (00000006, 00000006, 00000000, 0022AE38)
0022AC38  610717EA  (610C0370, 0022AC90, 0000006B, 0022AE38)
0022AE28  0059BEF2  (00000016, 00427680, 0022CE60, 005C2490)
0022D678  004278B1  (00000000, 00000001, 0022D697, 00000001)
0022D698  00427D2C  (00000000, 00C025D8, 00001A28, 0000A695)
0022F738  0042B0BC  (00000001, 005FADF0, 00000000, 00000003)
0022F768  00430EE4  (00000005, 0022F840, 00000040, 6107F684)
0022FA58  0050E975  (00000002, 00000001, 00000000, 0A0467A0)
0022FEB8  0050B31D  (00000004, 0A0403E0, 7C4E91AA, 00000001)
0022FEF0  004DBB2E  (00000004, 615E0644, 0A040328, 0022FF24)
0022FF40  61007418  (610C3A28, FFFFFFFE, 000003D4, 610C394C)
0022FF90  610076FD  (00000000, 00000000, FFFFFFFF, 80430D04)
End of stack trace (more stack frames may be present)LOG:  startup process (pid 4504) was terminated by signal 6
LOG:  aborting startup due to startup process failure


Visit our website at http://www.rm.com

This message is confidential.  You should not copy it
or disclose its contents to anyone.  You may use and apply the information
only for the intended purpose.  Internet communications are not secure and
therefore RM does not accept legal responsibility for the contents of this
message.  Any views or opinions presented are only those of the author and
not those of RM.  If this email has come to you in error please delete it
and any attachments.  Please note that RM may intercept incoming and
outgoing e-mail communications.

This email has been scanned for viruses by Trend ScanMail.

^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: No space left on device
@ 2004-02-12 22:18  Bjoern Metzdorf <bm@turtle-entertainment.de>
  parent: Veera Sivakumar <vsivakumar@rm.com>
  2 siblings, 0 replies; 9+ messages in thread

From: Bjoern Metzdorf @ 2004-02-12 22:18 UTC (permalink / raw)
  To: Veera Sivakumar <vsivakumar@rm.com>; +Cc: pgsql-admin

> PANIC:  ZeroFill failed to write 
> /usr/share/postgresql/data/pg_xlog/xlogtemp.3452: No space left on device

your disk is full..

Regards,
Bjoern



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: No space left on device
@ 2004-02-12 23:04  Will LaShell <will@lashell.net>
  parent: Veera Sivakumar <vsivakumar@rm.com>
  2 siblings, 0 replies; 9+ messages in thread

From: Will LaShell @ 2004-02-12 23:04 UTC (permalink / raw)
  To: Veera Sivakumar <vsivakumar@rm.com>; +Cc: pgsql-admin

Veera Sivakumar wrote:

> Hi
> I am using Postgres Database  version 7.3.1.
> I am getting following error when I am starting postmaster. I could 
> not be able to start the postmaster.
> Pl help me
>
> Regard
> Shiva Kumar
> PANIC:  ZeroFill failed to write 
> /usr/share/postgresql/data/pg_xlog/xlogtemp.3452: No space left on 
> device                       
>
<SNIP>

Umm  well my first guess is that you are out of drive space. I assume 
you checked that already?

Will



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: No space left on device
@ 2004-02-13 00:29  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Veera Sivakumar <vsivakumar@rm.com>
  2 siblings, 0 replies; 9+ messages in thread

From: Tom Lane @ 2004-02-13 00:29 UTC (permalink / raw)
  To: Veera Sivakumar <vsivakumar@rm.com>; +Cc: pgsql-admin

"Veera Sivakumar" <vsivakumar@rm.com> writes:
> I am getting following error when I am starting postmaster. I could not be =
> able to start the postmaster.

> PANIC:  ZeroFill failed to write /usr/share/postgresql/data/pg_xlog/xlogtem=
> p.3452: No space left on device

Seems like you're out of disk space.

If you think you have space left, maybe the postmaster is being started
under a ulimit or disk-quota limit that's too tight?

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* No Space Left On Device
@ 2005-06-16 12:03  Lim Swee Nyin <snlim@taylori.com>
  0 siblings, 1 reply; 9+ messages in thread

From: Lim Swee Nyin @ 2005-06-16 12:03 UTC (permalink / raw)
  To: pgsql-admin

hi There,

When I was fine tuning my already running application, all of the sudden, I couldn't perform any save/edit operation on my database, with the error such as:

ERROR: could not extend relation 4273000/17231/926549: No space left on device SQL = update call set personal=1 where rowid=8735 

I tried to update/insert several other tables but the more or less the same message appear. 

I should have more than enough disk space on my system:

$ dfspace
/                   : Disk space: 15775.57 MB of 21868.99 MB available (72.14%)
/stand              : Disk space:    34.51 MB of    39.99 MB available (86.28%)
/home               : Disk space: 13258.27 MB of 15000.00 MB available (88.39%)
/tmp                : Disk space:  1023.92 MB of  1024.00 MB available (99.99%)
/var/tmp            : Disk space:  1023.92 MB of  1024.00 MB available (99.99%)

where my postgres DB is on "/". and the strange thing is, the databas have been running fine for about 4 months.

can any one help please?

Thanks a lot.

Lim

^ permalink  raw  reply  [nested|flat] 9+ messages in thread

* Re: No Space Left On Device
@ 2005-06-21 10:13  Grega Bremec <gregab@p0f.net>
  parent: Lim Swee Nyin <snlim@taylori.com>
  0 siblings, 0 replies; 9+ messages in thread

From: Grega Bremec @ 2005-06-21 10:13 UTC (permalink / raw)
  To: Lim Swee Nyin <snlim@taylori.com>; +Cc: pgsql-admin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lim Swee Nyin wrote:
| hi There,
|
| When I was fine tuning my already running application, all of the
| sudden, I couldn't perform any save/edit operation on my database, with
| the error such as:
|
| ERROR: could not extend relation 4273000/17231/926549: No space left on
| device SQL = update call set personal=1 where rowid=8735
|
| I tried to update/insert several other tables but the more or less the
| same message appear.

Hello, Lim.

You're not telling much, apart from the amount of disk space dfspace
reports. What we'd need to know to be able to (start to) help you is at
least the following things:

~ - What operating system is that (i *assume* SCO OpenServer)?
~ - What filesystem?
~ - Does the filesystem support any kinds of special features that could
~   make it possible for a situation like that to take place?

| I should have more than enough disk space on my system:
|
| $ dfspace
| /    : Disk space: 15775.57 MB of 21868.99 MB available (72.14%)

The first thought that occurred to me was the percentage of disk space
that is considered by the system to be reserved for the super-user, and
given that this is your root filesystem, it _may_ well have been
predominantly allocated to the super-user, as you have /home, /tmp and
/var/tmp mounted on other filesystems.

Also, I don't know how quota reports excess to user processes on
OpenServer, if that's the case you're running. Might even look like
running out of space.

But then again, it may be something completely different. :)

Hope this helps.

Kind regards,
- --
Grega Bremec
gregab at p0f dot net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCt+hYfu4IwuB3+XoRAveFAJ4mBHPHjFeTq2Nj1A0aHhG38VhBMgCfU+RW
OgFvrUlf7TLpnN2lHWFSRQQ=
=tbul
-----END PGP SIGNATURE-----



^ permalink  raw  reply  [nested|flat] 9+ messages in thread


end of thread, other threads:[~2005-06-21 10:13 UTC | newest]

Thread overview: 9+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-12-31 17:27 No Space left on Device Jose <javalis@sympatico.ca>
2003-01-02 00:27 ` John Burski <jburski@cloudnet.com>
2003-01-02 05:26 ` Tom Lane <tgl@sss.pgh.pa.us>
2004-02-11 15:12 No space left on device Veera Sivakumar <vsivakumar@rm.com>
2004-02-12 22:18 ` Re: No space left on device Bjoern Metzdorf <bm@turtle-entertainment.de>
2004-02-12 23:04 ` Re: No space left on device Will LaShell <will@lashell.net>
2004-02-13 00:29 ` Re: No space left on device Tom Lane <tgl@sss.pgh.pa.us>
2005-06-16 12:03 No Space Left On Device Lim Swee Nyin <snlim@taylori.com>
2005-06-21 10:13 ` Re: No Space Left On Device Grega Bremec <gregab@p0f.net>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox