Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18000: Access method used by matview can be dropped leaving broken matview - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #18000: Access method used by matview can be dropped leaving broken matview
Date
Msg-id ZJtst5BUaRnH6JSj@paquier.xyz
Whole thread Raw
In response to Re: BUG #18000: Access method used by matview can be dropped leaving broken matview  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #18000: Access method used by matview can be dropped leaving broken matview  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Tree view 
On Tue, Jun 27, 2023 at 11:23:32AM -0700, Andres Freund wrote:
> Should we check changeDependencyFor()'s return value? On a first glance it
> looks like it would be an error to return 0 in this case?

Agreed.  I was wondering if this was worth having in this path (other
code paths are rather lax about that), but yes let's do it as there
should not be more than one record in pg_depend.
--
Michael
Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
Next
From: Michael Paquier
Date:
Subject: Re: BUG #18000: Access method used by matview can be dropped leaving broken matview