Обсуждение: Postmaster running out of discspace; Data corruption?

Hi,
one of our servers did accidently run out of discspace during a huge
data load. Postmaster closed the connection with `no space left on
device, cannot write x_log' or something similar. We have fsync=false on
that machine. Do we have to fear data corruption? Postmaster continued
as normal (without a restart) after we freed some space on the drive and
did a VACUUM FULL.

Thanks in advance

Hannes Dorbath <light@theendofthetunnel.de> writes:
> one of our servers did accidently run out of discspace during a huge
> data load. Postmaster closed the connection with `no space left on
> device, cannot write x_log' or something similar. We have fsync=false on
> that machine. Do we have to fear data corruption?

No.  The reason PG treats out-of-xlog-space as a PANIC is exactly so
that it won't do anything it can't log safely.  Once you get past the
postmaster restart you're fine.

            regards, tom lane

ok :)

Thank you

On 05.04.2005 18:11, Tom Lane wrote:
> Hannes Dorbath <light@theendofthetunnel.de> writes:
>
>>one of our servers did accidently run out of discspace during a huge
>>data load. Postmaster closed the connection with `no space left on
>>device, cannot write x_log' or something similar. We have fsync=false on
>>that machine. Do we have to fear data corruption?
>
>
> No.  The reason PG treats out-of-xlog-space as a PANIC is exactly so
> that it won't do anything it can't log safely.  Once you get past the
> postmaster restart you're fine.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
>