I've been fighting with moving a PostgreSQL database from 7.1.3 to 7.2.1, on a
Win2k SP2 box with NTFS cygwin 1.3.10, cygipc , and found that the backend
would stop on me everytime pg_restore tried to restore a very large
largeobject (like 100+ Megabytes). The error displayed would be:
FATAL 2: link from /d/postgresql_data/pg_xlog/0000000000000047 to /d/postgresql
_data/pg_xlog/000000000000004F (initialization of log file 0, segment 79)
failed: Permission denied
After poking around in the source, I came up with the basically the same patch
I now see you guys were discussing just recently on the pgsql-cygwin archives,
where src/backend/access/transam/xlog.c is altered to use rename() instead of
link()/unlink() - as BeOS does.
So if people need another way to reproduce the problem, one way at least for
me is to create a new database, import a single extremely large (100+mb)
object, pg_dump it with something like: pg_dump -b -Ft -f foo.pgdump.tar
mydbname, and then try to restore it with something like: pg_restore -Ft -d
It'll only take one or two tries for the backend to bail out.
So maybe there is something funky going on with link/unlink, and rename would
be a better choice on cygwin.
pgsql-cygwin by date
|Next:||From: Infodine||Date: 2002-04-29 18:29:54|
|Subject: plpgsql won't work|
|Previous:||From: Jason Tishler||Date: 2002-04-29 13:00:27|
|Subject: Re: hello|