Re: Subscription test 013_partition.pl fails under CLOBBER_CACHE_ALWAYS
От | Amit Kapila |
---|---|
Тема | Re: Subscription test 013_partition.pl fails under CLOBBER_CACHE_ALWAYS |
Дата | |
Msg-id | CAA4eK1LRwumMPmzsMpHhG1y3nwzLzXqmdOiQVUpzj6jwNC++3g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Subscription test 013_partition.pl fails under CLOBBER_CACHE_ALWAYS (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Subscription test 013_partition.pl fails under CLOBBER_CACHE_ALWAYS
|
Список | pgsql-hackers |
On Wed, Sep 16, 2020 at 1:16 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > I wrote: > It's not really clear to me why setting localreloid to zero is a sane > way to represent "this entry needs to be revalidated". I think a > separate flag would be more appropriate. Once we have lock on the > target relation, it seems to me that no interesting changes should > be possible as long as we have lock; so there's no very good reason > to destroy useful state to remind ourselves that we should recheck > it next time. > So, can we assume that the current code can only cause the problem in CCA builds bot not in any practical scenario because after having a lock on relation probably there shouldn't be any invalidation which leads to this problem? -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: