RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
От | Hayato Kuroda (Fujitsu) |
---|---|
Тема | RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 |
Дата | |
Msg-id | OSCPR01MB14966952C546AE32654B84AACF56EA@OSCPR01MB14966.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
|
Список | pgsql-bugs |
Dear Sawada-san, > > 1. > > USE_ASSERT_CHECKING has not been used to change the value yet. The main > usage is > > to call debug functions in debug build. > > I think we have a similar precedent such as MT_NRELS_HASH to improve > the test coverages. Oh, good detection, it seems a typical way. > > 2. > > If we add tests which is usable only for debug build, it must be run only when it > > is enabled. IIUC such test does not exist yet. > > I think we need to test cases not to check if we reach a specific code > point but to check if we can get the correct results even if we've > executed various code paths. As for this bug, it is better to check > that it works properly in a variety of cases. That way, we can check > overflow cases and non-overflow cases also in test cases added in the > future, improving the test coverage more. Best regards, Hayato Kuroda FUJITSU LIMITED
В списке pgsql-bugs по дате отправления: