[ADMIN] Converting 7.2 to 6.5 database
Hi all, anyone here knows how can I convert a 7.2 database to 6.5 database format ??? -- Leandro Rodrigo Saad Cruz (WEBMAIL) IT - Inter Business Tecnologia e Servicos (IB) http://www.ibnetwork.com.br - This mail sent through IMP: http://horde.org/imp/ ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [ADMIN] jdbc compile does not work
I had similar failures with JSDK 1.4, I used 1.3.1_03 instead and everything was ok. The build.xml file for the JDBC driver looks for a special class for deciding between J2EE and J2SE, but there were some changes between 1.3 and 1.4, so this way doesn't work. Egon "Ravi K.R." wrote: > JDBC compile did not work. > > problems faced during installation of postgreSQL7.2.1 version on linux > during compilation with java/jdbc support which gave error messages and was > not compiled. > > 1. Ant java based build tools was successfully installed and classpath was > set. > > 2. to build the driver --with-java option was added to configure command > line. > > $./configure --with-java > > 3. Then when I issued the 'make' command it gave the following errors > $make > > compile: > [javac] Compiling 53 source files to > /usr/local/src/postgresql-7.2.1/src/int > erfaces/jdbc/build > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/j > dbc2/ResultSet.java:60: org.postgresql.jdbc2.ResultSet should be declared > abstra > ct; it does not define getURL(int) in org.postgresql.jdbc2.ResultSet > [javac] public class ResultSet extends org.postgresql.ResultSet > implements j > ava.sql.ResultSet > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/j > dbc2/Statement.java:25: org.postgresql.jdbc2.Statement should be declared > abstra > ct; it does not define getMoreResults(int) in org.postgresql.jdbc2.Statement > [javac] public class Statement extends org.postgresql.Statement > implements j > ava.sql.Statement > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/j > dbc2/Connection.java:37: org.postgresql.jdbc2.Connection should be declared > abst > ract; it does not define setHoldability(int) in > org.postgresql.jdbc2.Connection > [javac] public class Connection extends org.postgresql.Connection > implements > java.sql.Connection > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/j > dbc2/DatabaseMetaData.java:40: org.postgresql.jdbc2.DatabaseMetaData should > be d > eclared abstract; it does not define supportsSavepoints() in > org.postgresql.jdbc > 2.DatabaseMetaData > [javac] public class DatabaseMetaData implements > java.sql.DatabaseMetaData > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/j > dbc2/PreparedStatement.java:32: org.postgresql.jdbc2.PreparedStatement > should be > declared abstract; it does not define setURL(int,java.net.URL) in > org.postgresq > l.jdbc2.PreparedStatement > [javac] public class PreparedStatement extends Statement implements > java.sql > .PreparedStatement > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/j > dbc2/CallableStatement.java:42: org.postgresql.jdbc2.CallableStatement > should be > declared abstract; it does not define > registerOutParameter(java.lang.String,int > ) in org.postgresql.jdbc2.CallableStatement > [javac] public class CallableStatement extends > org.postgresql.jdbc2.Prepared > Statement implements java.sql.CallableStatement > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/l > argeobject/PGblob.java:26: org.postgresql.largeobject.PGblob should be > declared > abstract; it does not define setBytes(long,byte[]) in > org.postgresql.largeobject > .PGblob > [javac] public class PGblob implements java.sql.Blob > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/l > argeobject/PGclob.java:26: org.postgresql.largeobject.PGclob should be > declared > abstract; it does not define setString(long,java.lang.String) in > org.postgresql. > largeobject.PGclob > [javac] public class PGclob implements java.sql.Clob > [javac]^ > [javac] > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/org/postgresql/x > a/ClientConnection.java:70: org.postgresql.xa.ClientConnection should be > declare > d abstract; it does not define setHoldability(int) in > org.postgresql.xa.ClientCo > nnection > [javac] final class ClientConnection > [javac] ^ > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -deprecation for details. > [javac] 9 errors > > BUILD FAILED > > /usr/local/src/postgresql-7.2.1/src/interfaces/jdbc/build.xml:72: Compile > failed > , messages should have been provided. > > Total time: 31 seconds > make[3]: *** [all] Error 1 > make[3]: Leaving directory > `/usr/local/src/postgresql-7.2.1/src/interfaces/jdbc' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/usr/local/src/postgresql-7.2.1/src/interfaces' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/usr/local/src/postgresql-7.2.1/src' > make: *** [all] Error 2 > > please someone help
[ADMIN] FATAL 1: Database "template0" is not currently accepting connections?
Out of the blue I received this error running 7.2 on win 2k FATAL 1: Database "template0" is not currently accepting connections the immediate query was a select on a database but not template0. I am curious to know if anyone has experienced this or might know the cause and / or cure. thanks don
Re: [ADMIN] postgres 7.2.1 and pam
Georg Lutz writes: > My pg_hba.conf looks like this: > --- > local all md5 > local all pam postgresql > --- Both of these entries apply to local connections, so the first one gets used and PAM is never considered. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] databases and RAID ...
On Fri, 24 May 2002, Kris Deugau wrote: [snip] KD> Note that if you're looking for a system you can hotswap, you will KD> probably need to go SCSI in any case; I'm not aware of any KD> hotswap-capable IDE RAID systems. Not exactly ;-) Promise TX2 and TX4 with special enclosures do the trick. If you need to scale further, 3Ware Escalade controllers (www.3ware.com) would be the right choice. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[ADMIN] two databases
I'd like to set up two databases on one server but need information on securing them separately. The databases will be accessed by different groups, who cannot have access to the data on the other database. I assume that this can be done using Postgres 7.1.3. Am I correct? The database that I currently have setup is enforcing sign-on using the pg_passwd utility. Would I just need a separate pg_passwd file for the new database? Do I need to create a new database cluster area? Can anyone point to some documentation on the best way to set this up? suggestions? Thank you Jodi ___Jodi L KanterBioInformatics Database AdministratorUniversity of Virginia(434) 924-2846[EMAIL PROTECTED]
Re: [ADMIN] two databases
Jodi- I've not actually tried this, but here is how I think you could set up a division such as you describe: Create two password files with pg_passwd. Edit pg_hba.conf to specify a different password file for each database: local database1 password passwords1 local database2 password passwords2 The lines above assume that you've got two databases, "database1" & "database2", with two corresponding password files, "password1" & "password2". It also assumes that your database is on the same machine as the users. If the database is on a different machine, you'd want to add the IP address(es) & mask & change local to host. -Nick -- Nick Fankhauser [EMAIL PROTECTED] Phone 1.765.935.4283 Fax 1.765.962.9788 Ray Ontko & Co. Software Consulting Services http://www.ontko.com/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jodi Kanter Sent: Tuesday, May 28, 2002 3:09 PM To: Postgres Admin List Subject: [ADMIN] two databases I'd like to set up two databases on one server but need information on securing them separately. The databases will be accessed by different groups, who cannot have access to the data on the other database. I assume that this can be done using Postgres 7.1.3. Am I correct? The database that I currently have setup is enforcing sign-on using the pg_passwd utility. Would I just need a separate pg_passwd file for the new database? Do I need to create a new database cluster area? Can anyone point to some documentation on the best way to set this up? suggestions? Thank you Jodi ___ Jodi L Kanter BioInformatics Database Administrator University of Virginia (434) 924-2846 [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [ADMIN] two databases
Le Mardi 28 Mai 2002 22:09, Jodi Kanter a écrit : > I'd like to set up two databases on one server but need information on > securing them separately. The databases will be accessed by different > groups, who cannot have access to the data on the other database. I assume > that this can be done using Postgres 7.1.3. Am I correct? The database that > I currently have setup is enforcing sign-on using the pg_passwd utility. > Would I just need a separate pg_passwd file for the new database? Do I need > to create a new database cluster area? Can anyone point to some > documentation on the best way to set this up? suggestions? > Thank you Please note that the stable version of PostgreSQL is 7.2.1. Documentation can be found at: - http://www.postgresql.org/idocs -> standard documentation - http://techdocs.postgresql.org -> technical notes - http://pgadmin.postgresql.org -> pgAdmin2 interface Cheers, Jean-Michel POURE ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
