Dne 9.7.2010 21:33, Robert Haas napsal(a):
2010/7/8 Pavel Baroš:
Description of patch:
1) can create MV, and is created uninitialized with data
CREATE MATERIALIZED VIEW mvname AS SELECT ...
This doesn't seem acceptable. It should populate it on creation.
Yes, it would be bette
Dne 9.7.2010 21:33, Robert Haas napsal(a):
2010/7/8 Pavel Baroš:
Description of patch:
1) can create MV, and is created uninitialized with data
CREATE MATERIALIZED VIEW mvname AS SELECT ...
This doesn't seem acceptable. It should populate it on creation.
Yes, it would be bette
Robert Haas napsal(a):
2010/6/25 Pavel Baros :
On http://github.com/pbaros/postgres can be seen changes and my attempt to
implement materialized views. The first commit to the repository implements
following:
Materialized view can be created, dropped and used in SELECT statement.
CREATE MAT
Heikki Linnakangas napsal(a):
On 12/06/10 17:18, Pavel Baros wrote:
I am curious how could I solve the problem:
During refreshing I would like to know, if MV is stale or fresh? And I
had an idea:
In fact, MV need to know if its last refresh (transaction id) is older
than any INSERT, UPDATE, DE
