erl's using its own memory allocator you'll want to
rebuild it to not do that.
--
Dan
--it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED]
At 3:14 PM -0500 3/24/05, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
... I'm pretty sure for embedding use it uses whatever routines
the embedder defines, but it's been a while since I've poked around
in there.
Hmm. plperl is definitely not doing anything
At 6:58 PM -0500 3/24/05, Greg Stark wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
Anyway, if perl's using its own memory allocator you'll want to rebuild it
to not do that.
You would need to do that if you wanted to use a debugging malloc. But
there's
no particular rea
ion.
--
Dan
--it's like this-------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
At 1:34 AM -0500 3/27/05, Madison Kelly wrote:
Dan Sugalski wrote:
At 12:31 AM -0500 3/27/05, Madison Kelly wrote:
Hi all,
After looking at the postres and perl docs plus some Googling I
can't seem to find the answer I am looking for. I hope maybe
someone here can help. ^_^
What I am t
ved?)
--
Dan
------it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
--
fers = 1000
> work_mem = 131072
> maintenance_work_mem = 131072
> max_stack_depth = 4096
> i tried work_mem with 512MB and 2MB and i get the
same error...
>
> i read all the post, but i don't know how i can
configure perl on
> Windows...
>
> thanks in advance
>
-it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
---(end of broadcast)
At 10:05 AM +0400 4/20/05, Alexandre wrote:
On Apr 19, 2005, at 23:24, Dan Sugalski wrote:
At 9:40 PM +0400 4/19/05, Alexandre wrote:
Lane, thank you, but it is not: PostISAM "generates SQL statements
on the fly from traditional ISAM (read, write, start) statements",
so it just add ove
8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
Dan
--it's like this---
Dan Sugalski even sam
s own:
Just out of curiosity, is this something that constant SQL (or SQL
generated by code) with placeholder variables won't protect against?
--
Dan
--it's like this-------
Dan Sugalski
ly doable, and worth looking into.
--
Dan
--it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
--it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
---(end of broadcast)--
At 1:01 AM -0500 3/10/07, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
I assume I'll have to do a 64 bit build to use more than a few gig of
shared buffers. If I do that, though, am I going to have to do a
database dump and reload,
Yes, most likely, because you'
At 7:47 PM +0100 3/10/07, Martijn van Oosterhout wrote:
On Sat, Mar 10, 2007 at 08:30:20AM -0500, Dan Sugalski wrote:
Possibly it won't. The machine the DB is on sees heavy access to
large files, to the point where parts of the database may get flushed
out of the OS buffer cache.
Preferences pane) with a shortname "postgres". The
problem is, this user already exists in my netinfo
database/domain
Note that fink installs a postgres
user.
--
Dan
--it's like
this-----
stgres user, amongst others, as part of the base
install. (Well, it's one of the strongly suggested packages, but
close enough since pretty much everyone puts it in)
--
Dan
--it's like this---
Dan Sugalski
ields? Is
there something simple and straightforward I can do to make this work
that I'm just missing here?
--
Dan
------it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED] have
At 2:37 PM -0400 10/25/04, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
I've got some SQL statements that I'm issuing from my app using the
PQexecParams() C call. All the parameters are passed in as literal
string parameters (that is, the paramTypes array entry for e
ck the error:
DB error is: ERROR: unsupported format code: 1043
I'm at a bit of a loss right now. What *should* I be using here? (Or
is there something simple that I'm missing?)
--
Dan
----------it's like this---
Dan Sugalski
At 3:41 PM -0400 10/26/04, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
DB error is: ERROR: unsupported format code: 1043
You're putting it in the format parameter, not the datatype parameter
D'oh! Darned reused array pointers...
Thanks.
--
fetch) Do I have to?
--
Dan
--it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
-
At 12:50 PM -0700 2/15/05, Michael Fuhr wrote:
On Tue, Feb 15, 2005 at 02:32:56PM -0500, Dan Sugalski wrote:
I've got some code that uses PQexecParams and does the equivalent of:
DECLARE a_cursor CURSOR FOR SELECT foo, bar FROM baz WHERE field = $1
FETCH NEXT a_cursor
but when I g
Dan
--it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
aren't
written in PHP, and write a simple compiler for it, so it wouldn't
happen tomorrow, but it's certainly doable)
--
Dan
------it's like this---
Dan Sugalski even samur
At 11:16 PM +0200 2/14/06, Marko Kreen wrote:
On 2/14/06, Dan Sugalski <[EMAIL PROTECTED]> wrote:
Zend isn't, last time I looked (which, granted, was ages ago), needed
to run PHP, but it may be now.
I guess you are thinking about "Zend - PHP Optimizer" not "Zen
At 10:39 AM -0400 9/7/04, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
Is there any way to convince explain to go do its thing when given a
query with placeholders in it?
PREPARE foo(...) AS SELECT ...
EXPLAIN EXECUTE foo(...)
EXPLAIN EXECUTE is a relatively
Is there anything I can do to speed this up, short of doing the
parameter substitution myself and skipping PQexecParams here? (Which
I'd rather not, since it's a pain and somewhat error-prone (for me,
at least))
--
Dan
------it's like this--
At 5:19 PM -0400 9/10/04, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
I'd figure, though, that since the parameters are being passed
into PQexecParams basically to get them out of band so I don't have
to deal with escaping, quoting, and suchlike things, that the
At 5:55 PM -0400 9/10/04, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
Would I regret it if I asked where in the source this lies so I could
go fix it?
If it were easy to fix it would have been fixed before now ...
Oh, I wasn't expecting it to be an *easy* fix... :) The
At 6:33 PM -0400 9/10/04, Tom Lane wrote:
Dan Sugalski <[EMAIL PROTECTED]> writes:
Since the only difference in this case is that the parameters are
pulled out for transport rather than being in band (a
properly-escaped string substitution could turn this case from a
PQexecParams call
Dan
--it's like this-------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
---(end of broadcast)--
UTF-8, UTF-16, and UTF-32 will all encode Unicode characters just fine.
--
Dan
--it's like this---
Dan Sugalski even samurai
[EMAIL PROTECTED]
33 matches
Mail list logo
