From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: fs full stops postmaster |
Date: | 2000-12-14 15:49:58 |
Message-ID: | 11C1E6749A55D411A9670001FA687963368180@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> When the filesystem fills and the txlog cannot be written,
> then the postmaster dies.
>
> postgres(at)s0188000zeu:/usr/postgres> time echo "copy
> journaleintrag from '/tmp/j.unl' delimiters '|';" | psql cusejoua
> FATAL 2: copy: line 64902, write(logfile 0 seg 2 off
> 6094848) failed: No space left on device
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
> connection to server was lost
>
> I think it shoud stay up and running, but deny any
> modification until the filesystem is extended.
This is an effect of the fact, that the file is not really created in its full size
even if ls shows the 16 mb. As an additional effect, the db does not
start up any more --> txlog corrupted.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Richards | 2000-12-14 15:55:32 | Re: (Updated) Table File Format |
Previous Message | Zeugswetter Andreas SB | 2000-12-14 15:41:04 | fs full stops postmaster |