[BUGS] Bug #593: postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library
Pertti Karppinen ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library Long Description In the RPM file postgresql-odbc-7.2-1PGDG.i386.rpm there exist a link /usr/lib/libpsqlodbc.so that points to libpsqlodbc.so.0.27. However there is no file libpsqlodbc.so.0.27 included. Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] Bug #592: postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library
Pertti Karppinen ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library Long Description postgresql-odbc-7.2-1PGDG.i386.rpm file has a symbolic link /usr/lib/libpsqlodbc.so pointing to libpsqlodbc.so.0.27. However the actual file libpsqlodbc.so.0.27 is not included. Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Bug #594: postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library
Jouko Pynnonen ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description postgresql-odbc-7.2-1PGDG.i386.rpm lacks the actual shared library Long Description The packet contains just a symbolic link "/usr/lib/libpsqlodbc.so" which points to "libpsqlodbc.so.0.27". The file is missing from the package. Sample Code gcc foo.c -lpsqlodbc No file was uploaded with this report ---(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
[BUGS] Bug #595: No connection with jdbc since update to 7.2
Norbert Pfaff ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
No connection with jdbc since update to 7.2
Long Description
Exception in thread "main" Etwas ungewöhnliches ist passiert. Bitte Teilen Sie diesem
Fehler mit: Exception: java.lang.NullPointerException
Stack Trace:
java.lang.NullPointerException
at org.postgresql.Connection.openConnection(Unknown Source)
at org.postgresql.Driver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at TestPostgreSQL.main(TestPostgreSQL.java:84)
End of Stack Trace
at org.postgresql.Driver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at TestPostgreSQL.main(TestPostgreSQL.java:84)
Sample Code
public class TestPostgreSQL {
public static void main(String argv[]) throws Exception {
// Load the driver class
//
Class.forName("org.postgresql.Driver");
// Try to connect to the DB server.
// We tell JDBC to use the "postgresql" driver
// and to connect to the "template1" database
// which should always exist in PostgreSQL.
// We use the username "postgres" and no
// password to connect. Since we're not accessing
// any tables but only an SQL function
// this should work.
//
Connection conn = DriverManager.getConnection(
"jdbc:postgresql://localhost:5432:template1","postgres","database");
// Set up and run a query that fetches
// the current date using the "now()" PostgreSQL function.
//
Statement stmt = conn.createStatement();
ResultSet rset = stmt.executeQuery("SELECT now();");
// Iterate through the rows of the result set
// (obviously only one row in this example) and
// print each one.
//
while (rset.next()) {
System.out.println(rset.getString(1));
}
// Close result set, statement and DB connection
//
rset.close();
stmt.close();
conn.close();
}
}
No file was uploaded with this report
---(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
[BUGS] BLOB support is broken in the 7.2/7.3 JDBC driver, works in 7.1 driver java.sql.SQLException: ERROR: oidin: error in "\377\330\377\340...I'm on Linux 2.4.16 using JDK 1.4.0 but it fails in 1.3.1 as well. Here's a quick reproducible test case:-- start --package sample.java.jdbc;import java.sql.*;import java.io.*;import java.util.*;class testBlob{ public static void main(String args[]) { new testBlob(); System.exit(0); } public testBlob() { System.out.println("Let's begin the test ..."); String v_username = "postgre"; String v_password = "postgre"; String v_database = "jdbc:postgresql://127.0.0.1/TEST"; PreparedStatement v_pstmt = null; try { DriverManager.registerDriver(new org.postgresql.Driver()); Connection v_conn = DriverManager.getConnection( v_database, v_username, v_password); v_conn.setAutoCommit(false); File v_file = new File("/home/postgre/something.jpg"); FileInputStream v_fis = new FileInputStream(v_file); v_pstmt = v_conn.prepareStatement( "insert into lob_test (id,data) values (?,?)"); v_pstmt.setInt(1,2); v_pstmt.setBinaryStream(2,v_fis,(int)v_file.length()); System.out.println("now you see me"); v_pstmt.executeUpdate(); System.out.println("now you don't"); v_conn.commit(); v_fis.close(); v_pstmt.close(); } catch (IOException e_io) { System.out.println(e_io); } catch (SQLException e_sql) { System.out.println(e_sql); } System.out.println("You'll only get here with the 7.1 driver!"); }}-- end --01010101010101010101010101010101010101010101010101Marc P. Lavergne [wk:407-648-6996]Product DevelopmentrichLAVA Corporation--"Anyone who slaps a 'this page is best viewed withBrowser X' label on a Web page appears to beyearning for the bad old days, before the Web,when you had very little chance of reading adocument written on another computer, another wordprocessor, or another network."-Tim Berners-Lee (Technology Review, July 1996)01010101010101010101010101010101010101010101010101-- 01010101010101010101010101010101010101010101010101Marc P. Lavergne [wk:407-648-6996]Product DevelopmentrichLAVA Corporation--"Anyone who slaps a 'this page is best viewed withBrowser X' label on a Web page appears to beyearning for the bad old days, before the Web,when you had very little chance of reading adocument written on another computer, another wordprocessor, or another network."-Tim Berners-Lee (Technology Review, July 1996) java.sql.SQLException: ERROR: oidin: error in "\377\330\377\340...I'm on Linux 2.4.16 using JDK 1.4.0 but it fails in 1.3.1 as well. Here's a quick reproducible test case:-- start --package sample.java.jdbc;import java.sql.*;import java.io.*;import java.util.*;class testBlob{ public static void main(String args[]) { new testBlob(); System.exit(0); } public testBlob() { System.out.println("Let's begin the test ..."); String v_username = "postgre"; String v_password = "postgre"; String v_database = "jdbc:postgresql://127.0.0.1/TEST"; PreparedStatement v_pstmt = null; try { DriverManager.registerDriver(new org.postgresql.Driver()); Connection v_conn = DriverManager.getConnection( v_database, v_username, v_password); v_conn.setAutoCommit(false); File v_file = new File("/home/postgre/something.jpg"); FileInputStream v_fis = new FileInputStream(v_file); v_pstmt = v_conn.prepareStatement( "insert into lob_test (id,data) values (?,?)"); v_pstmt.setInt(1,2); v_pstmt.setBinaryStream(2,v_fis,(int)v_file.length()); System.out.println("now you see me"); v_pstmt.executeUpdate(); System.out.println("now you don't"); v_conn.commit(); v_fis.close(); v_pstmt.close(); } catch (IOException e_io) { System.out.println(e_io); } catch (SQLException e_sql) { System.out.println(e_sql); } System.out.println("You'll only get here with the 7.1 driver!"); }}-- end --01010101010101010101010101010101010101010101010101Marc P. Lavergne [wk:407-648-6996]Product DevelopmentrichLAVA Corporation--"Anyone who slaps a 'this page is best viewed withBrowser X' label on a Web page appears to beyearning for the bad old days, before the Web,when you had very little chance of reading adocument written on another computer, another wordprocessor, or another network."-Tim Berners-Lee (Technology Review, July 1996)01010101010101010101010101010101010101010101010101-- 01010101010101010101010101010101010101010101010101Marc P. Lavergne [wk:407-648-6996]Product DevelopmentrichLAVA Corporation--"Anyone who slaps a 'this page is best viewed withBrowser X' label on a Web page appears to beyearning for the bad old days, before the Web,when you had very little chance of reading adocument written on another computer, another wordprocessor, or another network."-Tim Berners-Lee (Technology Review, July 1996)
BLOB support is broken in the 7.2/7.3 JDBC driver, works in 7.1 driver
though. Basically, returns an error like the following on executeUpdate():
java.sql.SQLException: ERROR: oidin: error in "\377\330\377\340...
I'm on Linux 2.4.16 using JDK 1.4.0 but it fails in 1.3.1 as well.
Here's a quick reproducible test case:
-- start --
package sample.java.jdbc;
import java.sql.*;
import java.io.*;
import java.util.*;
class testBlob
{
public static void main(String args[])
{
new testBlob();
System.exit(0);
}
public testBlob()
{
System.out.println("Let's begin the test ...");
String v_username = "postgre";
String v_password = "postgre";
String v_database = "jdbc:postgresql://127.0.0.1/TEST";
PreparedStatement v_pstmt = null;
try
{
DriverManager.registerDriver(new org.postgresql.Driver());
Connection v_conn = DriverManager.getConnection(
v_database, v_username, v_password);
v_conn.setAutoCommit(false);
File v_file = new File("/home/postgre/something.jpg");
FileInputStream v_fis = new FileInputStream(v_file);
v_pstmt = v_conn.prepareStatement(
"insert into lob_test (id,data) values (?,?)");
v_pstmt.setInt(1,2);
v_pstmt.setBinaryStream(2,v_fis,(int)v_file.length());
System.out.println("now you see me");
v_pstmt.executeUpdate();
System.out.println("now you don't");
v_conn.commit();
v_fis.close();
v_pstmt.close();
}
catch (IOException e_io)
{
System.out.println(e_io);
}
catch (SQLException e_sql)
{
System.out.println(e_sql);
}
System.out.println("You'll only get here with the 7.1 driver!");
}
}
-- end --
01010101010101010101010101010101010101010101010101
Marc P. Lavergne [wk:407-648-6996]
Product Development
richLAVA Corporation
--
"Anyone who slaps a 'this page is best viewed with
Browser X' label on a Web page appears to be
yearning for the bad old days, before the Web,
when you had very little chance of reading a
document written on another computer, another word
processor, or another network."
-Tim Berners-Lee (Technology Review, July 1996)
01010101010101010101010101010101010101010101010101
---(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
[BUGS] Initdb Hangs
I can't seem to get Postgres initialized. When I run initdb it seems to hang. If I run it in the background and then try to run postmaster, postmaster complains that it cannot find template1. Looking in the directories, I see no files. Below is the result of running initdb with the debug option on. This is the version that came with Cygwin last week. Is there a way to discern the version number of Postgres from the command line? I'm running under Cygwin on Windows 2000 Professional. $ Initdb -d Running with debug mode on. Initdb variables: PGDATA=/postgres datadir=/usr/share/postgresql PGPATH=/usr/bin TEMPFILE=/tmp/initdb.1300 MULTIBYTE=SQL_ASCII MULTIBYTEID=0 POSTGRES_SUPERUSERNAME=Administrator POSTGRES_SUPERUSERID=500 TEMPLATE1_BKI=/usr/share/postgresql/template1.bki GLOBAL_BKI=/usr/share/postgresql/global.bki TEMPLATE1_DESCR=/usr/share/postgresql/template1.description GLOBAL_DESCR=/usr/share/postgresql/global.description POSTGRESQL_CONF_SAMPLE=/usr/share/postgresql/postgresql.conf.sample PG_HBA_SAMPLE=/usr/share/postgresql/pg_hba.conf.sample PG_IDENT_SAMPLE=/usr/share/postgresql/pg_ident.conf.sample This database system will be initialized with username "Administrator". This user will own all the data files and must also own the server process. Creating directory /postgres Creating directory /postgres/base Creating directory /postgres/global Creating directory /postgres/pg_xlog Creating template1 database in /postgres/base/1 Running: /usr/bin/postgres -boot -x1 -C -F -D/postgres -d template1
Re: [BUGS] Initdb Hangs
The version of Postgresql is 7.1.3-2 -Original Message- From: Blossom, Eric Sent: Monday, February 11, 2002 4:01 PM To: 'Report bugs to' Subject: Initdb Hangs I can't seem to get Postgres initialized. When I run initdb it seems to hang. If I run it in the background and then try to run postmaster, postmaster complains that it cannot find template1. Looking in the directories, I see no files. Below is the result of running initdb with the debug option on. This is the version that came with Cygwin last week. Is there a way to discern the version number of Postgres from the command line? I'm running under Cygwin on Windows 2000 Professional. $ Initdb -d Running with debug mode on. Initdb variables: PGDATA=/postgres datadir=/usr/share/postgresql PGPATH=/usr/bin TEMPFILE=/tmp/initdb.1300 MULTIBYTE=SQL_ASCII MULTIBYTEID=0 POSTGRES_SUPERUSERNAME=Administrator POSTGRES_SUPERUSERID=500 TEMPLATE1_BKI=/usr/share/postgresql/template1.bki GLOBAL_BKI=/usr/share/postgresql/global.bki TEMPLATE1_DESCR=/usr/share/postgresql/template1.description GLOBAL_DESCR=/usr/share/postgresql/global.description POSTGRESQL_CONF_SAMPLE=/usr/share/postgresql/postgresql.conf.sample PG_HBA_SAMPLE=/usr/share/postgresql/pg_hba.conf.sample PG_IDENT_SAMPLE=/usr/share/postgresql/pg_ident.conf.sample This database system will be initialized with username "Administrator". This user will own all the data files and must also own the server process. Creating directory /postgres Creating directory /postgres/base Creating directory /postgres/global Creating directory /postgres/pg_xlog Creating template1 database in /postgres/base/1 Running: /usr/bin/postgres -boot -x1 -C -F -D/postgres -d template1
Re: [BUGS] Initdb Hangs
"Blossom, Eric" <[EMAIL PROTECTED]> writes: > I can't seem to get Postgres initialized. When I run initdb it seems to > hang. > I'm running under Cygwin on Windows 2000 Professional. Did you start cygipc (ipc-daemon, or whatever it's called) first? regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] Postgresql 7.1.3 not thread safe
> In article <[EMAIL PROTECTED]>, Alain Picard ><[EMAIL PROTECTED]> writes: ap> This contrived example is the simplest form I can reproduce the ap> problem to. My actual application is written in lisp, and uses ap> unixODBC to talk to postgresql, though I believe the above problem ap> should be reproducible using any client. I might write a perl ap> script using the DBD stuff to test this. If I can reproduce the ap> problem there, I'll forward the script. I've included such a script, and it does reproduce the problem. Run it as follows 1) create the table as per the previous message 2) run two copies of the scripts CONCURRENTLY. % ./bang.pl 2 a 200 & % ./bang.pl 2 b 200 & 3) When both scripts have finished, run the query select * from test_table where data !='' and data != ''; in psql, which should return no records in postgres is working OK. You may have to run with a higher number of hits, or with more concurrent processes, to increase your chances of failure, especially on slow machines. bang.pl Description: perl test harness ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
