Re: [BUGS] Problem compiling postgresql 7.3b2
I think I found the problem... I only had static libbind, I recompiled bind to make shared libraries too, and now postgresql compiles without error. On 2002.10.07 21:23 Peter Eisentraut wrote: > Where did the file /usr/local/lib/libbind.a come from? Who installed > it > and what's in it? And can you show us the config.log file? > > Pierre writes: > > > I try to compile postgresql-7.3b2 on my GNU/Linux system with > gcc-3.2 > > There was no problem with the configure but for the make i got this > : > > > > [...] > > gmake[3]: Leaving directory > `/tmp/postgresql-7.3b2/src/backend/utils' > > gcc -O3 -march=i686 -Wall -Wmissing-prototypes > -Wmissing-declarations > > -L/usr/local/ssl/lib -Wl,-rpath,/usr/local/pgsql/lib -export-dynamic > > access/SUBSYS.o bootstrap/SUBSYS.o catalog/SUBSYS.o parser/SUBSYS.o > > commands/SUBSYS.o executor/SUBSYS.o lib/SUBSYS.o libpq/SUBSYS.o > > main/SUBSYS.o nodes/SUBSYS.o optimizer/SUBSYS.o port/SUBSYS.o > > postmaster/SUBSYS.o regex/SUBSYS.o rewrite/SUBSYS.o storage/SUBSYS.o > > tcop/SUBSYS.o utils/SUBSYS.o -lpam -lssl -lcrypto -lkrb5 -lz > -lreadline > > -ltermcap -lbind -lcrypt -lresolv -lnsl -ldl -lm -o postgres > > > /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/../../../libbind.a(irs_data.o): > > In function `__net_data_init': > > irs_data.o(.text+0x1ab): undefined reference to > `pthread_getspecific' > > irs_data.o(.text+0x1de): undefined reference to > `pthread_setspecific' > > irs_data.o(.text+0x21c): undefined reference to `pthread_key_create' > > > /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/../../../libbind.a(irs_data.o): > > In function `__res_state': > > irs_data.o(.text+0x26b): undefined reference to > `pthread_getspecific' > > irs_data.o(.text+0x2af): undefined reference to > `pthread_setspecific' > > irs_data.o(.text+0x2ed): undefined reference to `pthread_key_create' > > > /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/../../../libbind.a(irs_data.o): > > In function `__h_errno': > > irs_data.o(.text+0x31b): undefined reference to > `pthread_getspecific' > > irs_data.o(.text+0x368): undefined reference to > `pthread_setspecific' > > irs_data.o(.text+0x3ab): undefined reference to `pthread_key_create' > > collect2: ld returned 1 exit status > > gmake[2]: *** [postgres] Error 1 > > gmake[2]: Leaving directory `/tmp/postgresql-7.3b2/src/backend' > > gmake[1]: *** [all] Error 2 > > gmake[1]: Leaving directory `/tmp/postgresql-7.3b2/src' > > gmake: *** [all] Error 2 > > > > > > > > > > It would be great if you could help me with this ! > > > > Best regards, > > > > Pierre. > > > > -- > Peter Eisentraut [EMAIL PROTECTED] > > > > ---(end of > broadcast)--- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to > [EMAIL PROTECTED]) > > ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[BUGS] Bug in date/time input format
Hi, I have detected a bug in the date / time input format used in an insert statement in Postgres 7.2.1-5 (Redhat 7.3). If I use the following format: 'Tue, 08 Oct 2002 10:01:02 +1300' then I get the following error: ERROR: Bad timestamp external representation 'Tue, 08 Oct 2002 10:01:02 +1300' However if I use this format: 'Tue, 08 Oct 2002 10:01:02 NZDT' it inserts ok. '+1300' is valid for New Zealand during the daylight saving period. Regards, Christopher Swan ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] Bug #794: JDBC 7.3 PreparedStatement.setNull(..) .setObject(.., null) throws exception
Olaf Liepelt ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description JDBC 7.3 PreparedStatement.setNull(..) .setObject(.., null) throws exception Long Description I'm using your JDBC driver 7.3 beta 1 (tested the developer one as well). Folowing steps i've done: - Connecting to the datatbase - Set the connection into transaction mode - Created a PreparedStatement Filled in the set column=? with setObject(column, Object); when an Object is null the PreparedStatement.executeUpdate() throws an exception: No value specified for parameter 3 at org.postgresql.core.QueryExecutor.sendQuery(QueryExecutor.java:143) at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:65) at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:468) at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:320) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48) at org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:197) at comrad.database.sql.DatabaseAccess.doUpdate(DatabaseAccess.java:1497) ... my stuff where parameter 3 was 'null'. The same happens if I'm using the method setNull(column, type). After the exception I'd like to rollback all changes. I get another exception when calling rollback(): java.sql.SQLException: ERROR: Attribute 'nullqrollback' not found at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126) at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Co nnection.java:449) at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Co nnection.java:432) at org.postgresql.jdbc1.AbstractJdbc1Connection.rollback(AbstractJdbc1C onnection.java:967) at comrad.database.sql.DatabaseAccess.endTransaction(DatabaseAccess.jav a:929) ... my stuff Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Bug in date/time input format
Christopher Swan writes: > Hi, I have detected a bug in the date / time input format used in an insert > statement in Postgres 7.2.1-5 (Redhat 7.3). > > If I use the following format: > > 'Tue, 08 Oct 2002 10:01:02 +1300' > > then I get the following error: Is there a spot in the documentation that leads you to believe that this format is supported? If not, then it's not a bug. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Bug #794: JDBC 7.3 PreparedStatement.setNull(..)
I cannot reproduce this bug on CVS tip, nor the 7.3b1 driver you mention.
I know about a month ago there was a problem with batched prepared
statements, but that does not seem to be the case here. Could you send a
complete example or at least some context as to what
comrad.database.sql.DatabaseAccess.doUpdate(DatabaseAccess.java:1497)
is attempting to do?
The following works for me...
import java.sql.*;
public class a {
public static void main(String args[]) throws Exception {
String sql = "CREATE TABLE t(a int, b int)";
Class.forName("org.postgresql.Driver");
Connection conn =
DriverManager.getConnection("jdbc:postgresql://localhost:5730/test","test","");
try {
Statement stmt = conn.createStatement();
stmt.executeUpdate(sql);
sql = "INSERT INTO t(a,b) VALUES (3,4)";
stmt.executeUpdate(sql);
stmt.close();
} catch(SQLException sqle) {
sqle.printStackTrace();}
sql = "UPDATE t SET a = ? WHERE b = ?";
PreparedStatement pstmt = conn.prepareStatement(sql);
pstmt.setObject(1,null);
pstmt.setInt(2,4);
pstmt.executeUpdate();
pstmt.close();
Statement stmt = conn.createStatement();
stmt.executeUpdate("DROP TABLE t");
stmt.close();
conn.close();
}
}
On Tue, 8 Oct 2002 [EMAIL PROTECTED] wrote:
> Olaf Liepelt ([EMAIL PROTECTED]) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short Description
> JDBC 7.3 PreparedStatement.setNull(..) .setObject(.., null) throws exception
>
> Long Description
> I'm using your JDBC driver 7.3 beta 1 (tested the developer one as well).
> Folowing steps i've done:
> - Connecting to the datatbase
> - Set the connection into transaction mode
> - Created a PreparedStatement
>
> Filled in the set column=? with setObject(column, Object);
> when an Object is null the PreparedStatement.executeUpdate() throws an exception:
> No value specified for parameter 3
> at org.postgresql.core.QueryExecutor.sendQuery(QueryExecutor.java:143)
> at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:65)
> at
>org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:468)
> at
>org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:320)
> at
>org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
> at
>org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:197)
> at comrad.database.sql.DatabaseAccess.doUpdate(DatabaseAccess.java:1497)
> ... my stuff
>
> where parameter 3 was 'null'.
>
> The same happens if I'm using the method setNull(column, type).
>
>
> After the exception I'd like to rollback all changes. I get another exception when
>calling rollback():
>
> java.sql.SQLException: ERROR: Attribute 'nullqrollback' not found
>
> at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:126)
> at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Co
> nnection.java:449)
> at org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Co
> nnection.java:432)
> at org.postgresql.jdbc1.AbstractJdbc1Connection.rollback(AbstractJdbc1C
> onnection.java:967)
> at comrad.database.sql.DatabaseAccess.endTransaction(DatabaseAccess.jav
> a:929)
> ... my stuff
>
>
>
> Sample Code
>
>
> No file was uploaded with this report
>
>
> ---(end of broadcast)---
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [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
Re: [BUGS] Bug in date/time input format
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Christopher Swan writes: >> If I use the following format: >> 'Tue, 08 Oct 2002 10:01:02 +1300' >> then I get the following error: > Is there a spot in the documentation that leads you to believe that this > format is supported? If not, then it's not a bug. It is a bug, because +1300 *should* be accepted. The fact that you can't get more than 180 degrees of longitude away from Greenwich has not deterred the politicians who set timezone rules :-(. I don't know of any -1300 time zone, but +1300 is used in the real world. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Postmaster crash!
Hi, I had make VACUUM command for table with about 20 rows, but postmaster daemon: /var/log/messages : Oct 9 13:45:05 stat /kernel: pid 76778 (postgres), uid 1003: exited on signal 11 (core dumped) The command is: isbs=# vacuum full verbose sessions; server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !# There are log messages of PostgreSQL: " 2002-10-09 13:45:05 DEBUG: server process (pid 76778) was terminated by signal 11 2002-10-09 13:45:05 DEBUG: terminating any other active server processes 2002-10-09 13:45:05 NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. 2002-10-09 13:45:05 NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. 2002-10-09 13:45:06 NOTICE: Message from PostgreSQL backend: The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. I have rolled back the current transaction and am going to terminate your database system connection and exit. Please reconnect to the database system and repeat your query. 2002-10-09 13:45:06 DEBUG: all server processes terminated; reinitializing shared memory and semaphores IpcMemoryCreate: shmget(key=6543001, size=127746048, 03600) failed: Cannot allocate memory This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 127746048 bytes), reduce PostgreSQL's shared_buffers parameter (currently 15200) and/or its max_connections parameter (currently 64)." I have never seen this before, my PostgreSQL have works hard for about half year. Why this had happend? After restarting PostgreSQL the same query complete without any problems. Remark: before this query I had make CLUSTER on three tables, first of these have about 3 million rows, a next two have about 100,000 rows, but all CLUSTERs had been finished good. isbs=# select version(); version - PostgreSQL 7.2.1 on i386-unknown-freebsd4.4, compiled by GCC 2.95.3 My database is in productional state, so it shouldn't have such problems. Should I better wait for 7.3 version or patch for this problem exists? --- best regards, Ruslan A Dautkhanov [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
