Igor Markovic wrote [10/17/2006 11:45 AM]:
I have some problems when I use a postgres (8.1) database on Windows and
using the PostgreSQLTarBackuper.
Problem 1: I have to set the database user to trusted in pg_hba.conf so
pg_dump doesn't have to fill in a password. If I don't do this, the
controller and console will hang because pg_dump will wait for a
password. (maybe building in a timeout when executing external commands
would be nice). This will also be a problem for the other postgres
backuper classes (I think) because they all use the
AbstractPostgreSQLBackuper class.
Hi Igor,
you may wish to try the "authentication=true" option on the postgresql
backuper definition in your vdb.xml. This will turn on the
authentication mode, allowing sequoia to feed the password you provide
on the CLC into pg_dump. This requires that "expect" be installed on
your controller host.
Problem 2: When I restore a dump, the output will give me an exception
telling me that the restore wasn't successfully. Well it isn't really a
problem (I think) because the database and tables are created and the
tables are populated. The command that didn't succeed is "PROCEDURAL
LANGUAGE plpgsql;" because of "language "plpgsql" already exists". So
doesn't look like a problem to me. Sequoia will only think it hasn't
succeeded because of this. Maybe someone knows a fix for this?
The language definitions are per database in postgresql (by default).
Since we drop the database prior to restore, the 'language "plpgsql"
already exists' error you get should not happen...
Did you, by accident, make the language definition global (creating it
in template1) after you made the dump ?
Alternatively, you may wish to ignore the error in the code of the backuper.
A+O.
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
