The following bug has been logged online:
Bug reference: 3523
Logged by: Julian
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux
Description:plpython crash
Details:
-- PostgreSQL 8.2.4 on x86_64-pc-linux-gnu, compiled by GCC
x86_64
Hi, this just cropped up on the Orion app-server list - someone there was
having trouble storing large objects via JDBC in Postgres using the standard
PreparedStatement.setBinaryStream() method. I tried the same test outside of
Orion using a simple command-line app and hit the same problem.
Pokin
List of relations
Schema | Name | Type | Owner | Size | Description
+--+---+----+-+-
public | bar | table | julian | 0 bytes | bar\
public | foo | table | julian | 0 bytes | foo
(2 rows)
$ p
ving that code entirely" mean?
> As a temporary workaround, the SQL text file that pg_restore produces
> by default seems to be valid, so you could pipe that into psql.
Hmm, right. So at least my existing dumps aren't useless. Thanks.
-Julian
signature.asc
Description: This is a digitally signed message part.
Tom Lane wrote:
> Julian Mehnle writes:
> > I'm subscribed to the pgsql-bugs list, so no need to CC me. :-)
>
> cc to people in the thread is the established practice on these lists.
> It provides a bit more robustness when the lists are busy or slow.
Got it. I'll
ow since this is drifting off topic.
-Julian
signature.asc
Description: This is a digitally signed message part.
