I think your question is a bit off-topic on this mailinglist. You should
probably post it to pgsql-general.
Anyway, perhaps you'd be interested in looking at
http://gborg.postgresql.org/project/pljava.
Regards,
Thomas Hallgren
- Original Message -
From: "venky" <[EMAIL PROTECTED]>
News
I need three new functions in the Server Programming Interface (SPI) when
mapping an ExecutionPlan to a Java prepared statement (Pl/Java project).
The execute method of the prepared statement needs to know if the result is
a ResultSet (SPI_cursor_open) or just a number indicated how many rows tha
"Thomas Hallgren" <[EMAIL PROTECTED]> writes:
> I need three new functions in the Server Programming Interface (SPI) when
> mapping an ExecutionPlan to a Java prepared statement (Pl/Java project).
These functions look reasonable, but where is the documentation patch?
regar
I assume the group agreed that adding XML to libpq was the way to handle
XML, with a hook in psql to call it.
I also see this copyright on one of the files:
+ * Hash Table Data Type
+ * Copyright (C) 1997 Kaz Kylheku <[EMAIL PROTECTED]>
+ *
+ * Free Software License:
+ *
+ * All rights are reser
Tom Lane wrote:
> "Thomas Hallgren" <[EMAIL PROTECTED]> writes:
> > I need three new functions in the Server Programming Interface (SPI) when
> > mapping an ExecutionPlan to a Java prepared statement (Pl/Java project).
>
> These functions look reasonable, but where is the documentation patch?
I a
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Peter Eisentraut wrote:
> > > Bruce Momjian wrote:
> > > > I assume the group agreed that adding XML to libpq was the way to
> > > > handle XML, with a hook in psql to call it.
> > >
> > > I'm not sure about that, but we certainly disagree with thi
Patch removed. Requires more discussion.
---
Brian Moore wrote:
> hello,
>
> please find attached my support for printing/exporting
> xml from postgresql. psql has been modified to take
> an additional command line argumen
This patch makes the "block on semaphore" interruptible by signals on
win32. Without this, you can't kill a backend when it's waiting on a
lock.
//Magnus
win32_semint.patch
Description: win32_semint.patch
---(end of broadcast)---
TIP 8: explain an
Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian wrote:
> > > I assume the group agreed that adding XML to libpq was the way to
> > > handle XML, with a hook in psql to call it.
> >
> > I'm not sure about that, but we certainly disagree with this kind
> > of nonstandard XML when the
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I assume the group agreed that adding XML to libpq was the way to handle
> XML, with a hook in psql to call it.
My recollection was that we had not agreed we liked this patch?
regards, tom lane
---(end of
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > I assume the group agreed that adding XML to libpq was the way to
> > handle XML, with a hook in psql to call it.
>
> I'm not sure about that, but we certainly disagree with this kind of
> nonstandard XML when there is a perfectly good standard o
Bruce Momjian wrote:
> I assume the group agreed that adding XML to libpq was the way to
> handle XML, with a hook in psql to call it.
I'm not sure about that, but we certainly disagree with this kind of
nonstandard XML when there is a perfectly good standard out there.
Removed. Adding new version.
---
Magnus Hagander wrote:
> Ok, so I know this is pretty ugly. But there is a bug in mingw (current
> release - it's fixed in the snapshot version) with regards to readdir()
> (see previous mai
We will document this on the win32 TODO list and remove this patch once
MinGW is fixed.
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
--
Hello!
Here is a patch that implements setitimer() on win32. With this patch
applied, deadlock detection and statement_timeout now works.
The file timer.c goes into src/backend/port/win32/.
The patch also removes two lines of "printf debugging" accidentally left
in pqsignal.h, in the console con
Peter Eisentraut wrote:
> David Fetter wrote:
> > > > \? for help with psql commands
>
> > If you wanted to pick one of the two patches, which one would it be?
> > If not, what should the patch look like?
>
> There seems to be a consensus on the form left standing above. That
> seems OK to me.
"Mark Cave-Ayland" <[EMAIL PROTECTED]> writes:
> Yup indeed. Please find enclosed the latest version of the analyze patch
> taking into account all the things we have discussed in the thread.
I've reviewed and applied this with some small changes. You did a good
job --- the only things you missed
Applied by Tom. Thanks.
---
Mark Cave-Ayland wrote:
> Hi Tom,
>
> > -Original Message-
> > From: Tom Lane [mailto:[EMAIL PROTECTED]
> > Sent: 02 February 2004 16:54
> > To: Mark Cave-Ayland
> > Cc: [EMAIL PROTECTE
Thomas, if this is ready for application, would you make some SGML
changes to match, or give me text to add for them. Thanks.
---
Thomas Hallgren wrote:
> I need three new functions in the Server Programming Interface (SPI)
Peter Eisentraut wrote:
> Gavin Sherry wrote:
> > This just clears up one aspect of variable handling in psql.
> > [ "variable names are case-sensitive" ]
>
> I honestly wonder why this is suddenly of so much interest. I hope no
> one is going to question the fact that the command names are
> c
Bruce Momjian <[EMAIL PROTECTED]> writes:
> We will document this on the win32 TODO list and remove this patch once
> MinGW is fixed.
IIRC, Tom and I both suggested that there is no need to clutter the
source tree with a temporary workaround for a platform that hasn't
even seen a stable release ye
Jan Wieck wrote:
> Attached is a corrected version that solves the query cancel problem by
> not napping any more and going full speed as soon as any signal is
> pending. If nobody objects, I'm going to commit this tomorrow.
Jan, three questions. First, is this useful now that we have the new
c
Jan Wieck wrote:
> Bruce Momjian wrote:
>
> > Jan Wieck wrote:
> >> Attached is a corrected version that solves the query cancel problem by
> >> not napping any more and going full speed as soon as any signal is
> >> pending. If nobody objects, I'm going to commit this tomorrow.
> >
> > Jan, th
23 matches
Mail list logo
