"Frédéric SURLEAU" <frederic.surleau@atosorigin.com> writes:
> On this system, the file size is limited using ulimit.=0D
> =0D
> When the limit is reached for a database file, Postgres does THIS :=0D
> =0D
> LOG: server process (pid 4820) was terminated by signal 25=0D
> LOG: terminating any other active server processes=0D
It would probably work to just ignore SIGXFSZ on systems that have it.
That would change the behavior into an error return from write(), which
we already know what to do with.
Note however that running PG under a filesize ulimit is a rather foolish
thing to do. Running out of space for an ordinary table is one thing,
but running out of space for pg_xlog or pg_clog will induce a system
panic not materially different from the above.
regards, tom lane
