From: | Celia McInnis <celia(dot)mcinnis(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Erik Wienhold <ewie(at)ewie(dot)name>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Dropping a temporary view? |
Date: | 2024-03-20 17:22:00 |
Message-ID: | CAGD6t7JkGN_=rMt+hBv1iyiCttvDTvGFULbYfWhaLgtUi=jYuw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Good, that's what I'd hope. I'm still not sure why it took more than 7
minutes in psql to select the old non-temporary view contents after
dropping the newer temporary view of the same name. There were no delays in
producing the original non-temporary view. If I can reproduce the problem
in psql, I'll re-ask. Meanwhile I'll also change my software to use
different view names when using non-temporary iviews for debugging.
Thanks,
Celia McInnis
On Wed, Mar 20, 2024 at 12:33 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wednesday, March 20, 2024, Celia McInnis <celia(dot)mcinnis(at)gmail(dot)com>
> wrote:
>>
>>
>> Is there some reason why it then took 7 minutes to select from the
>> non-temporary view tempview after I dropped the temporary view tempview?
>>
>>>
>>>
> The fact that you had and then dropped the temporary view has no
> relationship to how some other unrelated view performs. That the views
> have the same name is just bad naming/design for this very reason; it harms
> understanding.
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bartosz Chroł | 2024-03-20 17:40:55 | pg_dumpall with flag --no-role-passwords omits roles comments as well |
Previous Message | Adrian Klaver | 2024-03-20 17:01:37 | Re: Dropping a temporary view? |