Daniel Gustafsson writes:
>> On 9 Jan 2020, at 10:34, Octopus ZHANG wrote:
>> I partially agree. But with the context, it doesn't assume we want
>> `view<->visualize` the data. It also says:
>>> Another use for a materialized view is to allow faster access to data
>>> brought across from a rem
> On 9 Jan 2020, at 10:34, Octopus ZHANG wrote:
Please don't top-post on the mailinglists.
> I partially agree. But with the context, it doesn't assume we want
> `view<->visualize` the data. It also says:
>
> >> Another use for a materialized view is to allow faster access to data
> >> broug
I partially agree. But with the context, it doesn't assume we want
`view<->visualize` the data. It also says:
>> Another use for a materialized view is to allow faster access to data
brought across from a remote system through a foreign data wrapper.
It is talking about 'the view' not the graph.
> On 9 Jan 2020, at 09:05, PG Doc comments form wrote:
If people want to be able to quickly graph historical sales data, ...
>
> This sentence doesn't make sense. I think it should be:
>
> --- If people want to be able to quickly grab/obtain/get historical sales
> data, ...
I'm not a nat
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/rules-materializedviews.html
Description:
Hi all,
This is the link to the page which has a typo.
https://www.postgresql.org/docs/10/rules-materializedviews.html. In the line
below the fou
