Dne 8.7.2010 12:33, Robert Haas napsal(a):
2010/6/29 Pavel Baroš:
Yeah, it is my fault, I did not mentioned that this patch is not final. It
is only small part of whole implementation. I wanted to show just this,
because I think that is the part that should not change much. And to show I
did
On Thu, Jul 8, 2010 at 9:22 AM, Robert Haas wrote:
> On Thu, Jul 8, 2010 at 9:09 AM, Pavel wrote:
>> Any update on this?
>>
>> Sure, sorry for delay, I updated code on http://github.com/pbaros/postgres
>> just a few minutes ago. Today I'll post patch here on HACKERS with my
>> comments.
>
> It's
On Thu, Jul 8, 2010 at 9:09 AM, Pavel wrote:
> Any update on this?
>
> Sure, sorry for delay, I updated code on http://github.com/pbaros/postgres
> just a few minutes ago. Today I'll post patch here on HACKERS with my
> comments.
It's a little hard for me to understand what's going on via the git
2010/6/29 Pavel Baroš :
> Yeah, it is my fault, I did not mentioned that this patch is not final. It
> is only small part of whole implementation. I wanted to show just this,
> because I think that is the part that should not change much. And to show I
> did something, I am not ignoring GSoC. Now I
2010/6/30 Robert Haas :
> By the way, does the SQL standard say anything about materialized views?
AFAIK, nope. Probably for the same reason that indexes are not
mentioned by the standard: both are only performance enhancements, and
one could easily imagine future SQL database systems that manage
2010/6/29 David Christensen :
> Do we see supporting the creation of a materialized view from a regular view,
> as in ALTER VIEW regular_view SET MATERIALIZED or some such?
I'm not sure. I think we should focus our efforts on (1) getting it
to work at all and then (2) improving the performance o
On Jun 29, 2010, at 3:31 PM, Pavel Baroš wrote:
> 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:
Mate
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
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 MATERIALIZED
On Sun, Jun 27, 2010 at 12:52:17PM +0100, Simon Riggs wrote:
> On Fri, 2010-06-25 at 20:24 +0200, Pavel Baros wrote:
>
> > ... also you can look at enclosed patch.
>
> No tests == no patch
This isn't quite how I'd have phrased it, and it would be nice if
nobody phrased advice quite this way. :)
On Fri, 2010-06-25 at 20:24 +0200, Pavel Baros wrote:
> ... also you can look at enclosed patch.
No tests == no patch
Always best to work on the tests first, so everybody can see the syntax
you are proposing, and also see if your patch actually works. Otherwise
you may find people disagree and t
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 MATERIALIZED VIEW mvname AS SELECT ...;
DROP MATERIAL
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 MATERIALIZED VIEW mvname AS SELECT ...;
DROP MATERIAL
13 matches
Mail list logo
