Re: Improper use about DatumGetInt32

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Improper use about DatumGetInt32
Дата
Msg-id X/kLBt7Dx+P78+9I@paquier.xyz
обсуждение исходный текст
Ответ на Re: Improper use about DatumGetInt32  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Ответы Re: Improper use about DatumGetInt32  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Список pgsql-hackers
On Fri, Jan 08, 2021 at 04:54:47PM +0100, Peter Eisentraut wrote:
> Updated patch that does that.

Thanks.  Looks sane seen from here.

+/* LCOV_EXCL_START */
Does it really make sense to add those markers here?  It seems to me
that we would ignore any new coverage if regression tests based on
older versions are added (we may really want to have such tests for
more in-core extensions to be able to verify the portability of an
extension, but that's not the job of this patch of course).

-       elog(ERROR, "block 0 is a meta page");
+       ereport(ERROR,
+               (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
+                errmsg("block 0 is a meta page")));
[...]
+                errmsg("block number %llu is out of range for relation \"%s\"",
This does not follow the usual style for error reports that should not
be written as full sentences?  Maybe something like "invalid block
number %u referring to meta page" and "block number out of range for
relation %s: %llu"?
--
Michael

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bharath Rupireddy
Дата:
Сообщение: Re: EXPLAIN/EXPLAIN ANALYZE REFRESH MATERIALIZED VIEW
Следующее
От: japin
Дата:
Сообщение: Re: EXPLAIN/EXPLAIN ANALYZE REFRESH MATERIALIZED VIEW