Thomas Hallgren [EMAIL PROTECTED] writes:
... The only thing that doesn't work
right now is a function that returns RECORD (not SETOF) since the rsinfo
in this case is NULL. Can you shed some light on that?
What's the test case exactly?
regards, tom lane
Tom Lane wrote:
You could do worse than to back-port get_call_result_type() into your
older branches and just leave out the code for the OUT parameter case.
Great advice! I went ahead and did just that. Now PL/Java handles
IN/INOUT/OUT parameters correctly with 8.1 and it handles functions
Tom Lane wrote:
Thomas Hallgren [EMAIL PROTECTED] writes:
... The only thing that doesn't work
right now is a function that returns RECORD (not SETOF) since the rsinfo
in this case is NULL. Can you shed some light on that?
What's the test case exactly?
thhal=# create function
Thomas Hallgren [EMAIL PROTECTED] writes:
thhal=# create function javatest.recordExample(int, int) returns record
as 'org.postgresql.pljava.example.ComplexReturn.complexReturn' immutable
language java;
CREATE FUNCTION
thhal=# select * from javatest.recordExample(3, 4) as (foo int, bar int,
Tom Lane wrote:
Thomas Hallgren [EMAIL PROTECTED] writes:
thhal=# create function javatest.recordExample(int, int) returns record
as 'org.postgresql.pljava.example.ComplexReturn.complexReturn' immutable
language java;
CREATE FUNCTION
thhal=# select * from javatest.recordExample(3, 4) as (foo
Tom,
BTW, as for your original question about performance, the current
external sort algorithm is mainly designed to conserve disk space,
not to be as fast as possible. It could probably be a good bit faster
if we didn't mind taking twice as much space (mainly because the
physical disk
Hi all,
Just wanted everyone to know what we're pulling CVS HEAD nightly so it
can be tested in STP now. Let me know if you have any questions.
Tests are not automatically run yet, but I hope to remedy that
shortly.
For those not familiar with STP and PLM, here are a couple of links:
STP
Mark,
Just wanted everyone to know what we're pulling CVS HEAD nightly so it
can be tested in STP now. Let me know if you have any questions.
Way cool.How do I find the PLM number? How are you nameing these?
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
On Tue, Apr 12, 2005 at 01:04:20PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
What about the simple one of having a bool pg_cast.castissystem
column, or something similar?
This one is sounding pretty good to me, though I'd be inclined to call
it castisbuiltin or some
convention I'm using is postgresql-MMDD, for example
postgresql-20050413, for the anonymous cvs export from today (April
13). I have a cronjob that'll do the export at 1AM PST8PDT.
The search page for the PLM numbers is here:
https://www.osdl.org/plm-cgi/plm?module=search
or you can
On Sun, 2005-04-10 at 21:12 -0400, Bruce Momjian wrote:
Jim C. Nasby wrote:
Maybe better for -hackers, but here it goes anyway...
Has anyone looked at compressing WAL's before writing to disk? On a
system generating a lot of WAL it seems there might be some gains to be
had WAL data
Hi guys,
After working on PHP for a few weeks, I see that what they do with their
interactive docs is have any comments posted get emailed to the docs
list. Do we do this?
That was, good comments are immediately integrated into the manual.
Chris
---(end of
I did 'gmake distclean' and rebuild and I still get the attached failures.
Chris
parallel group (13 tests): text name char varchar boolean oid int8 int2 float4
int4 float8 bit numeric
boolean ... ok
char ... ok
name ... ok
varchar
On Thu, Apr 14, 2005 at 09:41:43AM +0800, Christopher Kings-Lynne wrote:
After working on PHP for a few weeks, I see that what they do with their
interactive docs is have any comments posted get emailed to the docs
list. Do we do this?
I think it's an interesting idea to mail the comments
On Thu, Apr 14, 2005 at 09:52:11AM +0800, Christopher Kings-Lynne wrote:
I did 'gmake distclean' and rebuild and I still get the attached failures.
Do you build in a separate directory? I do and I do have problems when
the grammars (main or plpgsql) get updated -- not sure why the derived
files
Do you build in a separate directory? I do and I do have problems when
the grammars (main or plpgsql) get updated -- not sure why the derived
files from bison and flex don't get rebuilt. I just delete them by
hand. (The build directory I just rm -fr as a whole).
Yours doesn't seem like a
On Thu, Apr 14, 2005 at 09:52:11AM +0800, Christopher Kings-Lynne wrote:
I did 'gmake distclean' and rebuild and I still get the attached failures.
What versions of PostgreSQL and FreeBSD? The FreeBSD machines in
the buildfarm look good.
http://www.pgbuildfarm.org/cgi-bin/show_status.pl
If
Alvaro Herrera [EMAIL PROTECTED] writes:
I think it's an interesting idea to mail the comments to pgsql-docs, but
*please don't* start emulating the PHP behavior regarding comments
(leaving the relevant ones forever) :-( I think the PHP manuals are
very low quality because of the information
It seems that's not much of a danger -- the interactive Postgres documentation
hardly gets any comments at all in the first place. It would be a big
improvement if there were some way to encourage many more comments.
Only link to the version with comments.
Chris
---(end of
19 matches
Mail list logo
