Sorry that i just joined the list and have to break the thread to reply to
Tom Lane's response on this @
http://www.postgresql.org/message-id/13741.1396275...@sss.pgh.pa.us
Note that the indexscan is actually *slower* than the seqscan so far as
> the table access is concerned; if the table were b
Hello,
My question is about multiprocess and materialized View.
http://www.postgresql.org/docs/9.3/static/sql-creatematerializedview.html
I (will) have something like 3600 materialised views, and I would like to
know the way to refresh them in a multithread way
(anderstand 8 cpu cores -> 8 refresh
On 4 April 2014 17:29, Nicolas Paris wrote:
> Hello,
>
> My question is about multiprocess and materialized View.
> http://www.postgresql.org/docs/9.3/static/sql-creatematerializedview.html
> I (will) have something like 3600 materialised views, and I would like to
> know the way to refresh them i
On Fri, Apr 4, 2014 at 2:31 AM, Varadharajan Mukundan
wrote:
> Sorry that i just joined the list and have to break the thread to reply to
> Tom Lane's response on this @
> http://www.postgresql.org/message-id/13741.1396275...@sss.pgh.pa.us
>
>
> Note that the indexscan is actually *slower* than th
Thanks,
"The only thing that immediately comes to mind would be running a
rather hacky DO function in 4 separate sessions:"
You mean 8 sessions I guess.
8 separate sessions ?
Have you any idea how to manage sessions ? Is it possible to create
separate session internaly ?
Do I have to make 8 exte
On 4 April 2014 20:49, PARIS Nicolas wrote:
> Thanks,
>
> "The only thing that immediately comes to mind would be running a
> rather hacky DO function in 4 separate sessions:"
> You mean 8 sessions I guess.
Yes, typo.
> 8 separate sessions ?
> Have you any idea how to manage sessions ? Is it po
On 4 April 2014 21:07, PARIS Nicolas wrote:
> Ok thanks,
>
> And what about triggers. 8 triggers based on the same event won't be
> multithreaded ?
I'm not clear on how triggers come into this. You can't have triggers
on materialized views, and they don't fire triggers on tables or views
that th
Ok thanks,
And what about triggers. 8 triggers based on the same event won't be
multithreaded ?
Le 04/04/2014 21:57, Thom Brown a écrit :
> On 4 April 2014 20:49, PARIS Nicolas wrote:
>> Thanks,
>>
>> "The only thing that immediately comes to mind would be running a
>> rather hacky DO functi
this postgres documentation :
http://www.postgresql.org/docs/9.3/static/ecpg-connect.html
says it is actually possible to manage connection in C stored procedure.
I may be wrong...
Le 04/04/2014 22:14, Thom Brown a écrit :
> lear on how triggers come into this. You can't have triggers
> on mate
On Fri, Apr 04, 2014 at 10:26:22PM +0200, PARIS Nicolas wrote:
> this postgres documentation :
> http://www.postgresql.org/docs/9.3/static/ecpg-connect.html
> says it is actually possible to manage connection in C stored procedure.
>
> I may be wrong...
>
>
> Le 04/04/2014 22:14, Thom Brown a éc
Hi Jeff,
It looks like the original emailer wrote a query that the planner is not
> smart enough to plan properly (A known limitation of that kind of query).
> He then made a bunch of changes, none of which worked. He then re-wrote
> the query into a form for which the planner does a better job
11 matches
Mail list logo
