Could have sworn this was already listed as a TODO, but can't see it on the
developer website. IMHO it's something that's needed, especially with
differing behaviour due to compiled plans.
--
Richard Huxton
Archonet Ltd
---(end of
Simon Riggs [EMAIL PROTECTED] writes:
Kenneth Marshall would like me to post this:
I agree that in order to manage today's large memory machines, we
need to have less contention in our buffer management strategies.
The two main main choke points are in the buffer hash table routines
and in the
Richard Huxton [EMAIL PROTECTED] writes:
Could have sworn this was already listed as a TODO, but can't see it on the
developer website. IMHO it's something that's needed, especially with
differing behaviour due to compiled plans.
See PREPARE and EXPLAIN EXECUTE.
Rod, can you lay out some psdueo code / logic involved in the process? I'm
guessing you lock the entry in pg_class, you up dependent objects, lock them,
update them all... is there more to it?
It was one an offline database at the time with only a single user -- so
locking wasn't a concern
plpgsql should be trying to coerce the return value to the functions return
type:
rms=# create or replace function retval(integer) returns text as ' begin
return $1::integer; end; ' language 'plpgsql';
CREATE FUNCTION
rms=# select retval(1) || ' is text';
?column?
---
1 is text
(1
Robert Treat [EMAIL PROTECTED] writes:
so ISTM that your example is certainly a deficiency if not a bug.
I believe it is a bug or at least an unimplemented feature in plpgsql:
plpgsql has its own implementation of casting, and is not aware that
casting to a domain should involve running check
elein [EMAIL PROTECTED] writes:
Shouldn't all function calls go (through fast path or fmgr
or the language manager?) to a centralized parameter marshalling?
We're talking about what happens inside the function, not how you pass
parameters to it.
regards, tom lane
Thomas Hallgren wrote:
How about,
Allow outside agents to extend the GUC variable set
Added:
* Allow external interfaces to extend the GUC variable set
---
- thomas
- Original Message -
From:
Hello,
I am trying to test some of my techniques, and for that i need the nested
loop join plan node (NestLoop) not to restart the scan of the inner relation
for a change of outer relation correlation value, instead start from the
current position where the search ended for the previous scan.
Hoping someone can help me figure out why I can't get PL/Tcl to load
without crashing the backend on Mac OS 10.3.2.
I compile Tcl, PostgreSQL, create the database and then run the
following:
create function plpgsql_call_handler() RETURNS LANGUAGE_HANDLER
as 'plpgsql.so' language 'c';
create
Nicolai Tufar [EMAIL PROTECTED] writes:
Under locale-ignorant FreeBSD it works fine.
But under Fedora Core 1 initdb it crashes under all
locales I tested -C, en_US, tr_TR with message given below.
Hmm. It seems that tr_TR has problems much more extensive than you've
indicated previously. I
I've looked into Olivier Hubaut's recent reports of 'Too many open
files' errors on OS X. What I find is that on Darwin, where we are
using Posix semaphores rather than SysV semaphores, each Posix semaphore
is treated as an open file --- it shows up in lsof output, and more to
the point it
Scott Goodwin [EMAIL PROTECTED] writes:
Hoping someone can help me figure out why I can't get PL/Tcl to load
without crashing the backend on Mac OS 10.3.2.
FWIW, pltcl seems to work for me. Using up-to-date Darwin 10.3.2
and PG CVS tip, I did
configure --with-tcl --without-tk
then
13 matches
Mail list logo
