On Mon, Jun 20, 2011 at 10:53 PM, Tom Lane wrote:
> Sushant Sinha writes:
>>> I guess you could poke the planner towards the bitmap scan by lowering
>>> the random_page_cost (the default value is 4, I'd say lowering it to 2
>>> should do the trick).
>
>> The numbers that I gave was after setting
On Mon, Jun 20, 2011 at 8:38 AM, Sushant Sinha wrote:
>
> postgres version 9.0.2
> statistics on docvector is set to 1 and as you can see the row
> estimates are fine.
>
> lawdb=# \d docmeta1
> Table "public.docmeta1"
> Column | Type | Modifiers
> -+---+
On 06/29/2011 02:14 PM, Greg Spiegelberg wrote:
Another alternative is to use GridSQL. I haven't used it myself but
seen it in action on a large install with 4 backend databases. Pretty
slick.
We actually demoed this as a proof of concept a while back. Even just
having two instances on the sa
On Wed, Jun 29, 2011 at 12:37 PM, Marinos Yannikos wrote:
> On Wed, 29 Jun 2011 13:55:58 +0200, Svetlin Manavski <
> svetlin.manav...@gmail.com> wrote:
>
> Question: Is there a way to get the same result from within a PL/pgSQL
>> function but running all the sub-queries in parallel? In case it i
On Wed, 29 Jun 2011 13:55:58 +0200, Svetlin Manavski
wrote:
Question: Is there a way to get the same result from within a PL/pgSQL
function but running all the sub-queries in parallel? In case it is not
directly available, which one would be the simplest way to implement it
in
my applicati
Hi all,
I am running PostgreSQL 9.0 on a number of nodes in an application level
cluster (there is different data on different machines). Currently a
PL/pgSQL function generates automatically aggregation queries like the
following:
(select * from appqosfe.F_total_utilization(13069188000::I
