Joshua D. Drake wrote:
With the new preload option is there any benefit/drawback to using
pl/Python versus pl/pgSQL?
If you're asking about relative speed, I did some *very* simple tests
and posted them here:
http://archives.postgresql.org/pgsql-patches/2003-07/msg00239.php
without preload:
===
"Marinos J. Yannikos" <[EMAIL PROTECTED]> writes:
> Shouldn't queries that use
> ... where t like '%something%'
> benefit from [an index on t] when t is NULL in almost all cases, since
> the query planner could use [it] to access the few non-NULL rows
> quickly?
No, and the reason is that the
Bill,
> Some functions they prototyped in MSSQL even return different types, based
> on certian parameters, I'm not sure how I'll do this in Postgres, but I'll
> have to figure something out.
We support that as of 7.4.1 to an extent; check out "Polymorphic Functions".
--
-Josh Berkus
Aglio Da
My understanding is that having NULL values in an index breaks it completely. Meaning
it won't be used in any query planning. Maybe I'm wrong though...
-Original Message-
From: Marinos J. Yannikos [mailto:[EMAIL PROTECTED]
Sent: Tue 1/27/2004 12:26 PM
To: [EMAIL PROTECTED]
Cc:
Shridhar Daithankar wrote:
Bill Moran wrote:
I have an application that I'm porting from MSSQL to PostgreSQL. Part
of this
application consists of hundreds of stored procedures that I need to
convert
to Postgres functions ... or views?
At first I was going to just convert all MSSQL procedures
Hi,
with the following table:
Table "public.foo"
Column | Type | Modifiers
+--+---
t | text |
Indexes:
"a" btree (t)
Shouldn't queries that use
... where t like '%something%'
benefit from "a" when t is NULL in almost all cases, since the query
planner could
Hello,
With the new preload option is there any benefit/drawback to using
pl/Python versus
pl/pgSQL? And no... I don't care that pl/Python is now considered untrusted.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, program
> Hello All
>
> Just wanted to gather opinions on what file system has the best balance between
> performance and
> reliability when used on a quad processor machine running SuSE64. Thanks
>
> DAve
I was reading the article 'Behind the ALTIX 3000' in the Feb. 2003 Linux Journal, and
it menti
PC Drew wrote:
I tested this out and saw no improvement:
I'd still suspect some class loading issues and HotSpot compilation
issues are polluting your numbers.Try using a PreparedStatement to
another table first in order to make sure that classes bytecode has been
loaded. There are som
I tested this out and saw no improvement:
EXPLAIN ANALYZE SELECT * FROM one;
Seq Scan on one (cost=0.00..20.00 rows=1000 width=404) (actual time=0.04..0.50
rows=51 loops=1)
Total runtime: 0.75 msec
EXPLAIN ANALYZE SELECT * FROM one;
Seq Scan on one (cost=0.00..20.00 rows=1000 width=404) (actual
Hi,
My personal feeling on this is, that the long time taken for the first query
is for loading all sorts of libraries, JVM startup overhead etc.
What if you first do some SELECT (whatever), on a different table, to warm
up the JVM and the database?
regards,
--Tim
THIS COMMUNICATION MAY CONTAI
11 matches
Mail list logo
