esn't scale well up as it'd have a linear algorithm
deep in its bowels.
What's the "real" story, then?
Thanks in advance.
2010/7/29 Vincenzo Romano :
> Hi all.
> I'm wondering about PGSQL scalability.
> In particular I have two main topics in my mind:
>
>
te table for the
"distinct volumes" could help even more.
--
Vincenzo Romano
Maybe Computers will never become as intelligent as
Humans. For sure they won't ever become so stupid.
---(end of broadcast)---
TIP 9: In versions below 8.
On Friday 30 March 2007 16:34 Dave Dutcher wrote:
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Vincenzo Romano
> >
> > Is there any "workaround"?
> >
> > In my opinion the later the query planner decisions are taken
On Friday 30 March 2007 01:12 Dave Dutcher wrote:
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Vincenzo Romano
> >
> > I thought that the query planner usually did a bad job on
> > function bodies
> > because they'd appea
as fast
as in the case of equality comparison.
I thought that the query planner usually did a bad job on function bodies
because they'd appear opaque to it.
In this case it seems to me that the body is opaque only if I use the "like"
operator.
Any hint?
--
Vincenzo Romano
-
issue, though I'm not sure whether this is an "expected feature" or
not.
Thanks a lot.
P.S.
I've seen hubert depesz lubaczewski's remark only on the web interface on
nabble.com. The email from the list manager never reached my mailbox!
On Sunday 18 March 2007 10:59 Vin
On Monday 19 March 2007 05:07 Tom Lane wrote:
> Vincenzo Romano <[EMAIL PROTECTED]> writes:
> > How can I delay the query planner decisions until the actual query is to
> > be done inside the function body?
>
> Use plpgsql's EXECUTE. AFAIR there is n
= 'TEST'::text) AND (reco_alphanum
< 'TESU'::text))
Filter: ((fiel_uniqueid = 2) AND (reco_alphanum ~~ 'TEST%'::text) AND
reco_isactive AND (reco_effectiv <= now()))
(3 righe)
| /PSQL |
Not only are query plans very different, but the equality qu
tual query is to be
done inside the function body?
Many thanks again for any hint.
On Sunday 18 March 2007 07:50 Vincenzo Romano wrote:
> Hi all.
>
> I'm experiencing a strange behaviour with 8.1.8 (cannot do upgrades to 8.2
> at the moment).
>
> On a 13+ million rows tabl
Hi all.
I'm experiencing a strange behaviour with 8.1.8 (cannot do upgrades to 8.2 at
the moment).
On a 13+ million rows table I can do a query with results back in less than
100 ms. Result is a set of bigint.
But when I encapsulate that query into an "SQL" function with three parameters
the resu
10 matches
Mail list logo
