t
that diff if anyone thinks it may help.
the environment variables PGUSER and PGPASSWORD are set earlier in the
script.
I've searched the archives of the mail lists, and found no references to
illegal seeks WRT running pg_dump.
Anyone got any clues ?
--
Simon Crute
-
"Allan Engelhardt" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> You'll want to ask on the perl groups, but briefly you get an illegal seek
when your command writes to the error file descriptor:
>
> % perl -e '`echo hi 1>&2` or warn "Oops: $! $?";'
> h
Hi,
If I have the WAL pointing to a different disk that the main postgres
database, and that other disk crashes (say writing to it blocks) what will
postgres do ? Will it continue to write OK to the main database, or will the
whole thing crash ? or hang waiting for the WAL writes to finish ?
T
Hi,
I'm trying to install & build DBD::Pg. against Postgres7.1
I've downloaded the latest version (0.98)
Postgres was installed via the RPMs. (base, lib, delel, perl, docs, test
and server)
it's a redhat 6.2 based system but with perl 5.6 installed.
perl Makefile.PL runs OK
make runs OK,
but w
Thanks for the answer, (and thanks to adb too)
>
> 7.1 has write-ahead logging (WAL), which does what you are looking for.
> See http://www.postgresql.org/devel-corner/docs/admin/wal.html
>
> The fsync mode also helps with data integiry, but it *really* slows down
> the system, unfortunately.
Loo
Hi all,
We're writing an app in Perl and currently using Oracle as the backend
database (via the perl DBI) but due to the costs when we put this live we're
thinking of useing Postgresql.
However we need to know how crash resistant Posgresql is. Oracle has the
"Archive log mode" which writes a l
