Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
От | Alexander Lakhin |
---|---|
Тема | Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25 |
Дата | |
Msg-id | e28ce947-4755-41cf-1460-4b92f4fbdc3a@gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25 (shihao zhong <zhong950419@gmail.com>) |
Ответы |
Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
|
Список | pgsql-bugs |
Hi Shihao, 23.10.2023 23:58, shihao zhong wrote: > Hi Alexander, > > This change makes sense to me. But I have a question here, because we already have a limitation in rel option level > and that will make sure the parameter is in 0.0001 - 0.25 range, this CHECK seems like a little redundant for me > especially it does not match the constraint in rel option. Maybe I missed some context here, but could we just remove > this CHECK? I had started this discussion with the same question, but Tom Lane proposed to reformulate the Assert [1] and I agree that it's for good. Index attribute options are checked when an index created, but then attoptions can be changed in pg_attribute, for example. I mean that such a check makes sense because there is an intermediate level between setting the option and using it. [1] https://www.postgresql.org/message-id/836412.1686502986%40sss.pgh.pa.us Best regards, Alexander
В списке pgsql-bugs по дате отправления: