It seems better to report no number at all rather than a number (INT_MAX) that
is known to be wrong.
What about Statement.executeUpdate? It has provision for returing a
batch execution response code.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
throwing an exception if we get something that is truly undecipherable?
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
object.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
getString() on a UUID field, it will
certainly work. Mapping the UUID to BLOB or CLOB is incorrect. I'm not
sure why your attempt to map it to a String didn't work, but you are
not convincing Hibernate to use a plain getString call.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs
bindings may not really be strings.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
().getAutoIncrement());
}
The driver should probably be changed to hand back the same
ResultSetMetaData instance each time instead of a new one for each
MetaData call.
Does this explain your problem? If not, can you provide more details on
how you access and use ResultSetMetaData?
Kris Jurka
--
Sent via
setObject(1, valor, Types.INTEGER) or
convert it prior to doing the setObject call to an appropriate
numeric type.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
to insert non-string data into a
properties object because all keys and values should be Strings. If you
get rid of properties.put(shutdown, Boolean.TRUE), it works just fine.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
to the wrong
implementation of acceptURL in the Postgres jdbc driver, connecting to any
other database is impossible.
I'm not sure what you mean. If you don't provide a database name, how do
you expect it to connect to different databases?
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql
-postgresql URL?
Kris Jurka
import java.sql.Driver;
public class Conn {
public static void main(String args[]) throws Exception {
String urls[] = {
jdbc:xx:postgresql,
jdbc:xx:postgresql:xx,
jdbc:xx:xx:postgresql,
jdbc:hsqldb:.,
jdbc:oraclethin:...
};
Driver driver = new
to change your application for some reason, you can
adjust the driver's binding behavior by using the stringtype=unspecified
connection parameter described here:
http://jdbc.postgresql.org/documentation/84/connect.html#connection-parameters
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql
schemas in the schema view.
This has already been fixed in CVS and will be in the next set of
releases.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
-refcursor
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
suppose we could try to inspect the Clob to determine if it was a PG Clob
or not and choose different methods based on that determination.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
did not include the Byte and Short data types when the JDBC 1.0
specification was finalized. The mapping of SMALLINT and TINYINT
to Integer is maintained to preserve backwards compatibility
For more information see table B-3 in the JDBC4.0 spec.
Kris Jurka
--
Sent via pgsql
fixed in CVS.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
standard ODBC escapes for portability, shouldn't you
be using {ts '2010-04-30 00:00:00'}?
http://msdn.microsoft.com/en-us/library/ms712360%28VS.85%29.aspx
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
it. You've got a couple of options:
1) Change the bytea format back to the 8.4 supported format. Set
bytea_output = escape in your postgresql.conf.
2) Build the JDBC driver from CVS which does support the new format.
3) Use an 8.4 server.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs
On Tue, 12 Jan 2010, Tom Lane wrote:
preparing something as trivial as a ROLLBACK is pretty silly so nobody
does it.
Actually the JDBC driver has been preparing BEGIN, COMMIT, and ROLLBACK
since the 8.0 release.
http://archives.postgresql.org/pgsql-jdbc/2006-10/msg00149.php
Kris Jurka
without a type (unknown), but it was
actually overwriting all types which could change the query's desired
behavior. In this case a safeguard to prevent that change was throwing
the exception noted.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
values.
Unfortunately that's failing and it's not what the user wants for this
case. I imagine the user really wants to get a Long back from this. I'm
going on vacation next week, but when I return, I'll make that happen.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
On Tue, 10 Nov 2009, Mauro Molinari wrote:
Bug reference: 5177
PostgreSQL version: 8.3.8
Description:Concurrency problem in AbstractJdbc23PooledConnection
Details:
Hello, we're using PostgreSQL JDBC3 driver 8.3-605 to connect to a 8.3.8
Postgres instance. Our application has a
to determine what projects in the entire postgresql
ecosystem deserve special mention on the bug reporting page.
Surely there must be at least one ODBC person subscribed to -bugs. What
about just asking them to be more responsive even if they don't have a
solution?
Kris Jurka
--
Sent via pgsql
to error out in this case.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
-8.3-603.jdbc3.jar
Right, postgis.jar is just an addon, and it's really a bug in the main
JDBC driver. I have put in a fix for this bug into the JDBC driver for
the next release. I've put up a copy of it here, and it should fix things
for you.
http://ejurka.com/pgsql/jars/arrdim/
Kris Jurka
-command statements you should use Statement.execute() and then
getResultSet or getUpdateCount until getMoreResults is false.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
' hashCode method doesn't work after the connection
is closed failing with a NullPointerException]
Fixed in CVS.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
case I'd be happy to look at it, but there's not much else I
can do.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
://archives.postgresql.org/pgsql-jdbc/2008-09/msg00102.php
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
)
at psqluuidtest.Main.main(Main..java:25)
Surely you want to persist a TestTable1 instance, not the uuid itself.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
, please post a
complete test case that shows the exact create table command and java code
calling getPrimaryKeys.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Wed, 21 May 2008, Kris Jurka wrote:
On Wed, 21 May 2008, Daniel Migowski wrote:
I came across a deadlock condition in the JDBC driver that rises when very
large queries, containing thousends of statements are send to the server
with statement.execute().
We already consider this case
must not
have autocommit on. Since the JDBC driver uses protocol level cursors
(portals), it doesn't even have the option of specifying WITH HOLD.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
into
multiple batches is that in autocommit mode you would get one transaction
per batch instead of the previous behavior of one transaction for the
whole execute call.
Kris Jurka
On Thu, 22 May 2008, Richard Evans wrote:
We hit this problem and modified the driver to use non-blocking IO to fix
into
an internal size that we expect is safe from deadlock. It looks like we
should be doing the same for these one query batches. I'm not sure how
tough that will be, but I'll take a look.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
the network
connection dropping that statement_timeout can't do.
In many cases statement_timeout is an adequate substitute for
setQueryTimeout, but not in the general case that the JDBC driver must
implement.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
accept the value and do nothing.
Kris Jurka
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Mon, 10 Mar 2008, Tom Lane wrote:
I'd be inclined to leave the mapping alone and just insert a warning
(or hard error) for inputs outside the range -1 to 1.
Here's a patch that errors out for out of range values.
Kris JurkaIndex: doc/src/sgml/func.sgml
');
This only works because it gets toasted before being put in the index.
Since you've selected something real compressible, you can fit 50k chars
into it.
Kris Jurka
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send
of the object although it can be a pain to type if you
writing a lot of queries by hand.
Kris Jurka
---(end of broadcast)---
TIP 6: explain analyze is your friend
the
other metadata calls appropriately.
Kris Jurka
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
/83rc1/
So it wouldn't hurt to try the above, but I don't have great hopes that it
will change things for you unless something got lost along the way.
Kris Jurka
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating
it be to do a search for a
schema with a quote in it's name using SQL identifier rules in Java code.
Kris Jurka
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
).
Kris Jurka
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
adjust this by the prepareThreshold URL parameter. You can disable
plan reuse by adding prepareThreshold=0.
Kris Jurka
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
to be 1638400. I don't know which is
correct.
You need to consider the units. guc.c is in number of pages, while
postgresql.conf is in kB. Since the page size is 8192, these are
equivalent.
Kris Jurka
---(end of broadcast)---
TIP 6: explain analyze
On Wed, 5 Dec 2007, Reece Hart wrote:
On Wed, 2007-12-05 at 23:20 -0500, Kris Jurka wrote:
You need to consider the units. guc.c is in number of pages, while
postgresql.conf is in kB. Since the page size is 8192, these are
equivalent.
I did consider that, but I'm not certain that it's
);
CREATE TABLE bittable (a bit(1), b bit(2));
SELECT COALESCE(a, b) FROM bittable;
CREATE TABLE bittable2 (a bit);
SELECT a FROM bittable2;
None of these ResultSets will contain length information sufficient to let
you know if you have bit(1) or bit(N) data.
Kris Jurka
solely on the length attribute is not good because the server
will not give you the length information in certain circumstances and
all you'll have is the raw bit type name. This is why we've chose to
use boolean as the server type for Types.BIT + BOOLEAN.
Kris Jurka
is really for multiple bits, not a single
bit. Consider SELECT 77::bit(8) results in 01001101. It's more
likely that you want to use boolean as the type instead although it
doesn't have any casts that will help you out in this situation either.
Kris Jurka
---(end of broadcast
;' language 'plpgsql' ;
Kris Jurka
Lance J. Andersen wrote:
Sorry Bad, Cut and paste. This test is a strip down of much larger
test. The reason the metadata is there as this gets run from a
framework which exercises JDBC drivers from all of the major vendors
which is also the reason
= err;
}
Why is this necessary? Since PSQLWarning overrides both getMessage and
toString, why is the super call needed?
Kris Jurka
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Thu, 18 Oct 2007, Kris Jurka wrote:
jurka=# create table t (c serial);
NOTICE: CREATE TABLE will create implicit sequence t_c_seq for serial
column t.c
CREATE TABLE
jurka=# select currval('t_c_seq');
currval
-
1
(1 row)
I would expect it to say that currval wasn't set
;
CREATE SEQUENCE
jurka=# select currval('myseq');
ERROR: currval of sequence myseq is not yet defined in this session
Kris Jurka
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http
;
CREATE SEQUENCE
jurka=# select nextval('s');
nextval
-
1
(1 row)
jurka=# select setval('s',5, false);
setval
5
(1 row)
jurka=# select currval('s');
currval
-
5
(1 row)
Should return 1 instead of 5.
Kris Jurka
---(end
On Sat, 13 Oct 2007, Jeremy Palmer wrote:
The following bug has been logged online:
Bug reference: 3675
PostgreSQL version: 8.3b1
Operating system: WinXP SP2
Description:Crash on xpath function with 2 parameters
Details:
The following query crashes the backend:
SELECT
.php
Kris Jurka
---(end of broadcast)---
TIP 1: 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
number of results that are returned.
The extended query protocol is designed around single query gives a
single result, so it isn't really prepared to handle the update count
and results at the same time.
Kris Jurka
---(end of broadcast)---
TIP 2
by a permission denied error because
you are running the tomcat server with a security policy. The driver
should be placed in $CATALINA_HOME/common/lib instead of a war file.
Kris Jurka
---(end of broadcast)---
TIP 7: You can help support
, unlike the getColumns() method. To reproduce run the following
statement in a database named test and the public schema:
Fixed in CVS for 8.1, 8.2, and HEAD.
Thanks for the test case.
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below
is implmented. So you'll need to cast the last parameter to an
integer to make it work with the current driver.
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan
to produce a good random number stream.
Kris Jurka
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Wed, 11 Apr 2007, Tom Lane wrote:
Kris Jurka [EMAIL PROTECTED] writes:
Why doesn't setseed complain when given a seed value outside of its
expected range?
Why should it complain? The use of the value is totally unspecified
anyway.
Because the user is likely using it incorrectly
On Wed, 11 Apr 2007, Tom Lane wrote:
It's not really possible to use it incorrectly, AFAICS. Any value you
might pass to it will result in a specific new seed value. Nowhere is
there any guarantee of what the mapping is, and it's obviously
impossible to guarantee that the mapping is
that our implementation is wrong and
it shouldn't return the doubled version and anyone interpolating text into
a query must escape it appropriately including the search string escape.
I'll put a fix for this into the next release.
Kris Jurka
---(end of broadcast
don't think
that's appropriate behavior for all users.
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
there just wouldn't be a
way to get at it on the database side.
Kris Jurka
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
(1,2) b;
a | b
---+---
1 | 1
1 | 2
2 | 1
2 | 2
3 | 1
3 | 2
4 | 1
4 | 2
(8 rows)
Tested on 8.1.3 and CVS HEAD.
Kris Jurka
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
of the JDBC2 spec, but was added in JDBC3.
So you'll need to download the JDBC3 version.
Kris Jurka
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
On Mon, 18 Sep 2006, Kiren Pillay wrote:
The following bug has been logged online:
Bug reference: 2636
PostgreSQL version: 8.1.4
Operating system: Windows
Description:JDBC error behaviour incorrect
Details:
try {
DBActions
be
returned as the vendor error code.
Perhaps the problem is that this page is referring to error codes when a
more careful reading shows that it is really talking about sql state
values?
http://www.postgresql.org/docs/current/static/errcodes-appendix.html
Kris Jurka
ofgetColumnName() return the real column'name.
please show why?thanks.
My project has been used Oracle and Mysql.It's my first to use PostgreSQL.
Please see the thread Wrong column names in ResultSetMetaData
http://archives.postgresql.org/pgsql-jdbc/2004-08/threads.php#8
Kris Jurka
the fetching of results from the ResultSet. I imagine you are using one
of the ResultSet.getXXX() methods using an improper column index.
Kris Jurka
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
a fix before the next official
releases. http://www.ejurka.com/pgsql/jars/gr/
Kris Jurka
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
' '::varchar(3) FROM tab retained the typmod value
specified in the query, but in 8.1 it is lost and -1 is used instead.
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index
On Wed, 14 Jun 2006, Bruce Momjian wrote:
Added to TODO list.
Already done.
http://archives.postgresql.org/pgsql-committers/2006-02/msg00299.php
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore
Bruce Momjian wrote:
Thanks for the feedback.
Patch attached, so NetBSD = 3.0 will not use float8-small-is-zero.
The buildfarm seems to think this is a bad idea.
http://pgbuildfarm.org/cgi-bin/show_log.pl?nm=gazelledt=2006-05-05%2016:30:00
Kris Jurka
---(end
. Here are
the functions:
I reported this here:
http://archives.postgresql.org/pgsql-bugs/2006-03/msg6.php
and it was fixed here:
http://archives.postgresql.org/pgsql-committers/2006-03/msg00021.php
This will be in 8.1.4 when released.
Kris Jurka
---(end of broadcast
eKol in #postgresql reported a problem with a plpgsql function crashing
the server. I tested the attached against 8.2cvs as of this morning
and got this stacktrace:
#0 plpgsql_xact_cb (event=XACT_EVENT_COMMIT, arg=0x0) at pl_exec.c:4521
#1 0x0046f43d in CallXactCallbacks
varying
Your options are to rewrite your query like:
INSERT INTO mytable (intcol) VALUES (CAST(? AS int))
or you may use the 8.2dev driver and add ?stringtype=unspecified to your
URL.
Kris Jurka
---(end of broadcast)---
TIP 5: don't forget
protocol if
that fails. To tell the driver you want a v2 protocol from the start add
?protocolVersion=2 to your URL.
Kris Jurka
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
win1251
FATAL: conversion between LATIN1 and WIN1251 is not supported
Previous connection kept
Kris Jurka
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
in
the javac tag in build.xml fixes this, but that's not a general
solution because it clearly won't be able to build other versions. Do you
have a better solution for runtime determination or specification of the
version we should try to build.
Kris Jurka
---(end
On Sat, 3 Dec 2005, Michael Fuhr wrote:
On Sat, Dec 03, 2005 at 07:53:23PM -0500, Kris Jurka wrote:
I'm seeing some date input overflows here.
Yep, I noticed this a few days ago while looking at another problem.
I probably should have started a new thread.
This seems to fix it.
Kris
I'm seeing some date input overflows here. I tested on CVS HEAD
without --enable-integer-datetimes and 7.4.9 and 8.0.4 with
--enable-integer-datetimes, so it appears to have been around for a
while:
jurka=# select '23456-01-01'::date;
date
---
5290466-07-05
(1 row)
kalisetty manideep wrote:
[Backend reports too many open connections]
But I am 100% sure that its not the issue with the
code.
Do you know any Postgresql - JDBC driver, which is not
from Postgresql development group. I think JDBC driver
is not closing the connection even though I am closing
failing to close connections.
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
limitation of server side prepared statements (which were
added in the 8.0 JDBC driver). You may not use the syntax INTERVAL ?,
but must instead use CAST(? AS INTERVAL) or ?::interval.
Kris Jurka
---(end of broadcast)---
TIP 4: Have you searched
to use when storing Blobs. You need to use
oid as the underlying type, or if you want to use bytea you need to use
setBytes or setNull(x, Types.BINARY).
Kris Jurka
---(end of broadcast)---
TIP 6: explain analyze is your friend
fixes I'm unaware of.
Kris Jurka
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
On Fri, 22 Jul 2005, Kris Jurka wrote:
On Fri, 22 Jul 2005, Andrus Adamchik wrote:
Whenver I call PreparedStatement.setNull(int, int) on BLOB or CLOB columns,
an exception below occurs. Driver version: postgresql-8.0-310.jdbc3.jar. But
looks like latest CVS version has the same problem
on Windows (yet).
Use some other database encoding.
Shouldn't we forbid its creation then? At least a strongly worded
warning? We see these complaints too often.
Kris Jurka
---(end of broadcast)---
TIP 2: you can get off all lists at once
.
Kris Jurka
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
to unique
constraints. If you've got a concrete reason why this is a bad thing
please let us know. The javadoc does indeed say primary key, but I don't
see why including unique ones as well is a problem.
Kris Jurka
---(end of broadcast)---
TIP 1
NULL, we should probably
cast this to name, or report the currently connected database name here.
Kris Jurka
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere
* FROM tclset(); -- works
SELECT tclset(); -- goes into an infinite loop
Kris Jurka
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
result, which is actually a
ResultSet.
Kris Jurka
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
With the promised files this time.
On Sat, 23 Apr 2005, Kris Jurka wrote:
The 8.1 server doesn't work when issuing queries using the v2 protocol,
notably the isnull bitmask in the DataRow message is incorrect. I suspect
the problem is with this commit:
http://archives.postgresql.org
set to true :
- this value should apply to Unique Index
If you check the javadoc for getIndexInfo you will see column four is
actually NON_UNIQUE not unique.
Kris Jurka
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go
...
There is a known bug in the 8.0 jdbc driver when the client and server are
in different timezones. Is that the case here?
Kris Jurka
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
1 - 100 of 185 matches
Mail list logo
