Hi.
I'm using the "Incremental Materialized View Maintenance" patch and have
reported the following issues.
(https://commitfest.postgresql.org/25/2138/)
To Suggest a "DROP INCREMENTAL MATERIALIZED VIEW" in psql, but the syntax
error when you run.
("DROP MATERIALIZED VIEW" command can drop Increme
Hi.
I found the problem after running "ALTER MATERIALIZED VIEW ... RENAME TO".
If a view created with "CREATE INCREMENT MATERIALIZED VIEW" is renamed,
subsequent INSERT operations to the base table will fail.
Error message.
```
ERROR: could not open relation with OID 0
```
Execution log.
```
[e
2019年12月3日(火) 14:42 Yugo Nagata :
> On Mon, 2 Dec 2019 13:48:40 -0300
> Alvaro Herrera wrote:
>
> > On 2019-Dec-02, Yugo Nagata wrote:
> >
> > > On Mon, 02 Dec 2019 10:36:36 +0900 (JST)
> > > Tatsuo Ishii wrote:
> > >
> > > > >> One thing pending in this development line is how to catalogue
> ag
SELECT statement that is not IMMUTABLE must not be specified when creating
a view.
An expression SELECT statement that is not IMMUTABLE must not be specified
when creating a view.
In the current implementation, a SELECT statement containing an expression
that is not IMMUTABLE can be specified whe
LIMIT clause without ORDER BY should be prohibited when creating
incremental materialized views.
In SQL, the result of a LIMIT clause without ORDER BY is undefined.
If the LIMIT clause is allowed when creating an incremental materialized
view, incorrect results will be obtained when the view is up
-defined type aggregate operation not supported by
INCREMENTAL MATERIALIZED VIEW?
An execution example is shown below.
```
[ec2-user@ip-10-0-1-10 ivm]$ cat extension-agg.sql
--
-- pg_fraction: https://github.com/nuko-yokohama/pg_fraction
--
DROP EXTENSION IF EXISTS pg_fraction CASCADE;
DROP TABLE
: operator does not exist
```
An execution example is shown below.
```
[ec2-user@ip-10-0-1-10 ivm]$ psql testdb -a -f extension-insert.sql
--
-- pg_fraction: https://github.com/nuko-yokohama/pg_fraction
--
DROP EXTENSION IF EXISTS pg_fraction CASCADE;
psql:extension-insert.sql:4: NOTICE: drop
) 17:12 Yugo NAGATA :
> On Thu, 16 Jan 2020 12:59:11 +0900
> nuko yokohama wrote:
>
> > Aggregate operation of user-defined type cannot be specified
> > (commit e150d964df7e3aeb768e4bae35d15764f8abd284)
> >
> > A SELECT statement using the MIN() and MAX() function
"ROW LEVEL SECURITY" and INCREMENTAL MATERIALIZED VIEW.
Hi.
If ROW LEVEL SECURITY is set for the source table after creating the
INCREMENTAL MATELIALIZED VIEW, the search results by that are not reflected.
After setting ROW LEVEL SECURITY (similar to normal MATERIALIZED VIEW), you
need to execute
Hi.
UNION query problem.(server crash)
When creating an INCREMENTAL MATERIALIZED VIEW,
the server process crashes if you specify a query with a UNION.
(commit id = 23151be7be8d8f8f9c35c2d0e4e5353aedf2b31e)
execute log.
```
[ec2-user@ip-10-0-1-10 ivm]$ psql testdb -e -f union_query_crash.sql
DR
Hi.
I understod that UNION is unsupported.
I also refer to the implementation of "./src/backend/commands/createas.c"
check_ivm_restriction_walker () to see if there are any other queries that
may be problematic.
2020年2月10日(月) 10:38 Yugo NAGATA :
> On Sat, 8 Feb 2020 11:15:45
MATERIALIZED VIEW.
(similar to handling non-immutable functions)
Regard.
2020年2月8日(土) 11:15 nuko yokohama :
> Hi.
>
> UNION query problem.(server crash)
>
> When creating an INCREMENTAL MATERIALIZED VIEW,
> the server process crashes if you specify a query with a UNI
12 matches
Mail list logo
