From: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Implementing Incremental View Maintenance |
Date: | 2020-02-27 21:35:55 |
Message-ID: | 1582839355247-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I have tried to use an other patch with yours:
> "Planning counters in pg_stat_statements (using pgss_store)"
> setting
> shared_preload_libraries='pg_stat_statements'
> pg_stat_statements.track=all
> restarting the cluster and creating the extension
> When trying following syntax:
> create table b1 (id integer, x numeric(10,3));
> create incremental materialized view mv1 as select id, count(*),sum(x)
> from b1 group by id;
> insert into b1 values (1,1)
>
> I got an ASSERT FAILURE in pg_stat_statements.c
> on
> Assert(query != NULL);
>
> comming from matview.c
> refresh_matview_datafill(dest_old, query, queryEnv, NULL);
> or
> refresh_matview_datafill(dest_new, query, queryEnv, NULL);
>
> If this (last) NULL field was replaced by the query text,
> a comment or just "n/a",
> it would fix the problem.
> Could this be investigated ?
Hello,
thank you for patch v14, that fix problems inherited from temporary tables.
it seems that this ASSERT problem with pgss patch is still present ;o(
Could we have a look ?
Thanks in advance
Regards
PAscal
--
Sent from:
https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2020-02-27 23:25:13 | Re: ALTER INDEX fails on partitioned index |
Previous Message | Tom Lane | 2020-02-27 21:11:05 | Re: Resolving the python 2 -> python 3 mess |