| From: | PARIS Nicolas <niparisco(at)gmail(dot)com> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: PGSQL 9.3 - Materialized View - multithreading |
| Date: | 2014-04-04 20:07:02 |
| Message-ID: | 533F10E6.4010303@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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 <niparisco(at)gmail(dot)com> 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 possible to create
>> separate session internaly ?
>> Do I have to make 8 external connection to database, to get 8 process.
>> It would be great if I could manage session internaly, in a pl/sql by
>> example.
>
> Well you can't have multiple sessions per connection, so yes, you'd
> need to issue each of them in separate connections.
>
> I can't think of a more convenient way of doing it, but the solution
> I've proposed isn't particularly elegant anyway.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2014-04-04 20:14:26 | Re: PGSQL 9.3 - Materialized View - multithreading |
| Previous Message | Thom Brown | 2014-04-04 19:57:19 | Re: PGSQL 9.3 - Materialized View - multithreading |