TED]]
Sent: Monday, November 27, 2000 11:16 PM
To: Rainer Mager
Cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] Postgres 7 pgdump problems
Rainer - sorry for the late reply, I haven't been at work for a few days!
Yeah, we've seen this happen before (on an old 6.3.2 database). At first
I j
Hi all,
I already reported this directly to Peter Mount but since I have since
joined this list I thought I should make it a more wide-spread report.
The issue is that if you use getDate() on a field that is a timestamp type
then you will get an SQLException that wraps a NumberFor
We have a Unicode (UTF-8) database that we are trying to upgrade to 7.1b4.
We did a pg_dumpall (yes, using the old version) and then tried a restore.
We hit the following 3 problems:
1. Some of the text is large, about 20k characters, and is multiline. For
almost all of the lines this was fine (p
Hi,
While trying 7.1b4 I got this using JDBC2:
ERROR: A request from 10.0.0.46 (10.0.0.46) resulted in
java.lang.NumberFormatException: 20 18:46:53+09
java.lang.NumberFormatException: 20 18:46:53+09
at java.lang.Integer.parseInt(Integer.java, Compiled Code)
at java.lang.Integ
Hi all,
I haven't been following the current thread on failed tests but I just had
some so I thought I'd mention it. If this is a repeat then I apologize.
I configured with:
./configure --enable-multibyte --enable-syslog --with-java --with-maxbackend
s=70
And the test
I tried to submit the results of my regression tests and got this:
Warning: PostgreSQL query failed: ERROR: parser: parse error at or near "t"
in
/home/projects/pgsql/developers/vev/public_html/regress/regress.php on line
359
Database write failed.
--Rainer
---(end of
Hi Peter and all,
I may have described this poorly, let me try again.
1. We have a Unicode database that has a particular dash character in it
that gets dumped incorrectly. When dumped (from 7.0.x) the dash becomes the
character 0xAD but is not properly encoded in UTF-8 (at least my limi
Sorry that I have no answer but I just loved this line...
> Even if I type it slowly and hit the keys very hard.
--Rainer
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
I noticed that 7.1 has officially been released. Does anyone know the status
of the bug I reported regarding encoding problems when dumping a 7.0 db an
restoring on 7.1?
Thanks,
--Rainer
---(end of broadcast)---
TIP 2: you can get off all lists
I posted yesterday regarding a memory leak I found in the JDBC driver in
7.1. I didn't check but it is quite likely it also existed in 7.0. The patch
I created hasn't been checked by anyone else yet so I don't know if it helps
for others or not. Feel free to try it.
--Rainer
> -Original Mess
I saw the problem in 2 different (but mirrored and therefore identical)
7.1.2 databases. The data was created in the db before 7.1.2 but it has
since been upgraded and the dump was via 7.1.2. Was the bug in the dump code
or did it have to do with db creation?
Thanks,
--Rainer
> -Original Me
to:[EMAIL PROTECTED]]On Behalf Of Peter Eisentraut
> Sent: Friday, August 24, 2001 12:15 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [BUGS] timestamps cannot be created without time zones
>
>
> > Rainer Mager ([EMAIL PROTECTED]) reports a bug with a severity of 2
Ok, I now understand more about how Postgres handles these older dates but
we're still seeing a problem that I'm not sure how to handle. Simply put, we
write a TIMESTAMP via JDBC and then read it back. What we write and what we
read are different. The only way I can think of fixing the problem is
Hi all,
Sorry to reopen this issue but I still think there is a bug somewhere,
perhaps in the JDBC driver. The code and the end of this message
demonstrates the bug. Basically I write a timestamp to the database and then
read it back and what I write and what I get back are different. I d
I posted this about 2 weeks ago and saw no further follow ups. Is this
timestamp thing not considered a bug? Or am I just doing something wrong?
Thanks,
--Rainer
> -Original Message-
> Sorry to reopen this issue but I still think there is a bug
> somewhere,
> perhaps in the JDBC dr
15 matches
Mail list logo