From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Empty materialized view |
Date: | 2024-03-24 20:50:06 |
Message-ID: | d77ae41c-0627-4999-b120-8b611af3d73f@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/24/24 13:36, Thiemo Kellner wrote:
> Am 24.03.2024 um 21:30 schrieb Adrian Klaver:
>> On 3/24/24 13:11, Thiemo Kellner wrote:
>> Confirmed in the same session that created it or in a different session?
>
> Different session, not knowing what that mattered
It does depending on the order of viewing. Namely if you viewed the
'old' empty MV in the outside session before you dropped/created the
'new' MV and committed the changes.
>
> Excerpt of the installation protocol:
> …
> ## tenth level ##
> Set materialised view QUERY_PER_TASK⠒MV up
> psql:views/QUERY_PER_TASK⠒MV.pg_sql:3: HINWEIS: materialisierte Sicht
> »query_per_task⠒mv« existiert nicht, wird übersprungen
> DROP MATERIALIZED VIEW
> SELECT 0
> REFRESH MATERIALIZED VIEW
> COMMENT
> COMMIT
> # insert data #
> …
>
> select count(*) from SNOWRUNNER.TASK_DEPENDENCY⠒V;
That is not the view you showed in your attached SQL in your previous
post nor what is mentioned above. Also if I am following your naming
scheme it is a regular view not a materialized view.
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Thiemo Kellner | 2024-03-24 20:58:52 | Re: Empty materialized view |
Previous Message | Thiemo Kellner | 2024-03-24 20:36:55 | Re: Empty materialized view |