> the driver what character set the backend is sending us? Can't
> it ask the backend dynamically?
>
This is what it actually does, isn't it? (Based on what I usually see in the
trace output on the backend.) I tested a unicode database with varchar(255)
fields and hungarian accented characters a
Hi,
I ran a few bench marks on JAVA writing to a postgreSQL table using and
found that for the same number of records added to the table as a
similar PERL routine the following results :
PERL 39 seconds : JAVA 45 Seconds.
In a similar experiment where PERL and JAVA did treir output to the
s
On 02 Sep 2001 03:35:29 +0200, you wrote:
>You don't need multibyte for iso-8859-1.
That's what I thought. But with current CVS (7.2) creating a
database with -E LATIN1 fails without multibyte support. See the
link in one of my previous postings in this thread.
Regards,
René Pijlman <[EMAIL PRO
> I ran a few bench marks on JAVA writing to a postgreSQL table
> using and
> found that for the same number of records added to the table as a
> similar PERL routine the following results :
> PERL 39 seconds : JAVA 45 Seconds.
> In a similar experiment where PERL and JAVA did treir output t
On Mon, 03 Sep 2001 07:47:29 +0200, you wrote:
>I ran a few bench marks on JAVA writing to a postgreSQL table using and
>found that for the same number of records added to the table as a
>similar PERL routine the following results :
> PERL 39 seconds : JAVA 45 Seconds.
>In a similar experimen
Hi!
On a busy server, serving web pages using tomcat and apache, I
get this error sometimes:
java.net.SocketException: errno: 48, error: Address already in
use for fd: 168
at java.net.PlainSocketImpl.socketConnect(Native
Method)
at
java.net.PlainSocketImpl.doConnect(PlainSocketI
On Mon, 03 Sep 2001 09:49:27 -0700, you wrote:
>Yes this is exactly what the driver does. It asks the server what
>character set is being used for the database. Unfortunatly the server
>only knows about character sets if multibyte support is compiled in. If
>the server is compiled without mu
Kovács Péter wrote:
>>the driver what character set the backend is sending us? Can't
>>it ask the backend dynamically?
>>
>>
>
> This is what it actually does, isn't it? (Based on what I usually see in the
> trace output on the backend.) I tested a unicode database with varchar(255)
> fields an
On Mon, 3 Sep 2001, andy wrote:
> Hi,
>
> I ran a few bench marks on JAVA writing to a postgreSQL table using and
> found that for the same number of records added to the table as a
> similar PERL routine the following results :
> PERL 39 seconds : JAVA 45 Seconds.
How did you start the te
i have several questions about the benchmark run that all come
down to one basic question - was the benchmark fair?
1) were you trying to test the performance of the languages or
were you trying to test the performance of the drivers? if
you are trying to test _languages_ then what you shou
I was wondering why it is that both PGpoint and PGcircle return a
"getColumnType" of ?
Is an arbirtrary number for "non-JDBC-standard type"? Or, could the
PG extended types be differentiated somehow? (e.g. and 1112)?
I am using the JBOSS ejb server, which makes use of the column
Barry Lind <[EMAIL PROTECTED]> writes:
> The multiple statements in one call is there for performance reasons.
> Please don't remove it entirely since it works fine in 7.1 and 7.2.
> Instead your fix should be conditional based on server version:
Given that someone else is proposing a patch tha
>From my POV there are two "costs" here:
1) The speed degradation by supporting multiple versions of postgres.
I tend not to be too concerned by speed, and more concerned with ease of
use. If speed really becomes an issue I can go into the code and remove
the offending inefficiency caused by sup
Andy,
I would be interesting in knowing what version you did this test on,
what platform, and most importantly which JDK (and if the Sun JDK which
JVM: classic, hotspot client, hotspot server).
thanks,
--Barry
andy wrote:
> Hi,
>
> I ran a few bench marks on JAVA writing to a postgreSQL tabl
I have added a description to the CVS and it will appear in 7.2. It is
in the development docs now.
> Hi Barry,
>
> I looked in the postgresql documentation and couldn't find any mention
> of a "bytea" type. Well actually, I found ..
>
> $ grep -i bytea *
> bki-commands.html:>bytea catalog-pg
I heard it was fixed too but looking around, I found nothing. I added
it tonight to the types section.
> Thomas,
>
> You are correct about the poor documentation for bytea. I hear this is
> fixed in 7.2 docs, but haven't verified. I learned about it myself by
> looking at the internal pg_*
I think it is important to support backward compatibility in code like
the JDBC driver. It is often the case that code opperates in an
environment where there may be servers at different release levels
(production databases on 7.0, while dev databases are on 7.1). Thus I
think that maintaini
17 matches
Mail list logo
