On Sat, Jan 21, 2017 at 9:53 PM, Tom Lane wrote:
> Amitabh Kant writes:
> > command: "/var/tmp/pgbin.SPOsRj4D/bin/pg_ctl" -w -l
> "pg_upgrade_server.log"
> > -D "/usr/local/pgsql/data91" -o "-p 50432 -b -c listen_addresses='' -c
> > unix_socket_permissions=0700 -c unix_socket_directory='/usr/
>
Hello,
we use a materialized view to aggregate datas from a very big table containing
logs.
The source table is partitioned, one table for a day.
Since the refresh of the materialized view seems to grow a lot about timing, we
would like to know if it is pssible to make a "partitioned materializ
Greetings,
* Job (j...@colliniconsulting.it) wrote:
> we use a materialized view to aggregate datas from a very big table
> containing logs.
> The source table is partitioned, one table for a day.
>
> Since the refresh of the materialized view seems to grow a lot about timing,
> we would like t
Hi Stephen.
>>The mat view takes longer and longer to update because it runs the full
>>query. What you really want to do is have a side-table that you update
>>regularly with appropriate SQL to issue UPDATE statements for just the
>>current day (or whatever).
If correct, i leave only last da
Greetings,
* Job (j...@colliniconsulting.it) wrote:
> >>The mat view takes longer and longer to update because it runs the full
> >>query. What you really want to do is have a side-table that you update
> >>regularly with appropriate SQL to issue UPDATE statements for just the
> >>current day