Re: [GENERAL] fast refresh materialized view

2016-02-11 Thread Michael Paquier
On Fri, Feb 12, 2016 at 4:29 AM, Oleg Bartunov wrote: > Похоже на то, что вы понимаете по-русски ! I don't. My bad. -- Michael -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] fast refresh materialized view

2016-02-11 Thread Michael Paquier
On Fri, Feb 12, 2016 at 1:56 AM, Nguyễn Trần Quốc Vinh wrote: > We would like to contribute to the PostgreSQL community. What can you > recommend us? If you are planning to send patches for integration into core Postgres, this code needs to be available under a license that is compatible with the

Re: [GENERAL] fast refresh materialized view

2016-02-11 Thread Oleg Bartunov
Похоже на то, что вы понимаете по-русски ! Сообщество примет вашу работу только под лицензией BSD. Если что непонятно, пишите мне. С Уважением, Олег On Thu, Feb 11, 2016 at 7:56 PM, Nguyễn Trần Quốc Vinh wrote: > We would like to contribute to the PostgreSQL community. What can you > recommend

Re: [GENERAL] fast refresh materialized view

2016-02-11 Thread Nguyễn Trần Quốc Vinh
We would like to contribute to the PostgreSQL community. What can you recommend us? Thank you. TS. Nguyễn Trần Quốc Vinh --- Chủ nhiệm khoa Tin học Trường ĐH Sư phạm - ĐH Đà Nẵng Website: http://it.ued.vn ; http://www.ued.vn

Re: [GENERAL] fast refresh materialized view

2016-02-09 Thread Michael Paquier
On Tue, Feb 9, 2016 at 12:32 AM, Nguyễn Trần Quốc Vinh wrote: > > Thank you very much. We did n't think about that. We would like to choose > APACHE LICENSE. We apologize for late reply. And that would be incompatible with the PostgreSQL license I guess, per concerns with patents and similar stuf

Re: [GENERAL] fast refresh materialized view

2016-02-08 Thread Nguyễn Trần Quốc Vinh
Thank you very much. We did n't think about that. We would like to choose APACHE LICENSE. We apologize for late reply. We would like to get discussion of the experts. Thanks and best regards, TS. Nguyễn Trần Quốc Vinh --- Chủ nhiệm khoa Tin học Trường

Re: [GENERAL] fast refresh materialized view

2015-12-03 Thread Jim Nasby
On 12/3/15 4:17 AM, Nguyễn Trần Quốc Vinh wrote: We have build a tool that generates all triggers in C-language for all data-changing events on all tables underlying upon query. The generated triggers do synchronous incremental updates for MV. Awesome! The hope is to eventually support this int

Re: [GENERAL] fast refresh materialized view

2015-12-03 Thread Nguyễn Trần Quốc Vinh
Dear Sir. I'm sorry. The attachment was too big. You can find the source code and the binary at *http://it.ued.udn.vn/myprojects/pgTriggerGen/PgSQLMVTriggersGenerator_v4._a_ * . Best regards. TS. Nguyễn Trần Quốc Vi

Re: [GENERAL] fast refresh materialized view

2015-12-03 Thread Nguyễn Trần Quốc Vinh
Dear Sir. I'm sorry. The attachment was too big. You can find the source code and the binary at http://it.ued.udn.vn/myprojects/pgTriggerGen/PgSQLMVTriggersGenerator v4._a_. Best regards. On Thu, Dec 3, 2015 at 5:17 PM, Nguyễn Trần Quốc Vinh wrote: > Dear Sirs. > > We have build a tool that ge

Re: [GENERAL] fast refresh materialized view

2015-11-15 Thread Michael Paquier
On Sat, Nov 14, 2015 at 7:01 AM, Pradhan, Sabin wrote: > Does postgres has fast refresh materialized view that supports incremental > refresh. In oracle , this is achieve by materialized view log. Not sure > how to implement it in postgres. No. Postgres offers just the possibility to refresh

Re: [GENERAL] fast refresh materialized view

2015-11-14 Thread Kevin Grittner
On Friday, November 13, 2015 4:02 PM, "Pradhan, Sabin" wrote: > Does postgres has fast refresh materialized view that supports > incremental refresh. In oracle , this is achieve by materialized > view log. Not sure how to implement it in postgres. There has been work toward that end, but f

[GENERAL] fast refresh materialized view

2015-11-13 Thread Pradhan, Sabin
Does postgres has fast refresh materialized view that supports incremental refresh. In oracle , this is achieve by materialized view log. Not sure how to implement it in postgres. Confidentiality Notice:: This email, including attachments, may include non-public, proprietary, confidential