Re: pg_stat_reset round 2
От
Neil Conway
Тема
Re: pg_stat_reset round 2
Дата
Msg-id
877kj5loyi.fsf@klamath.dyndns.org
Ответ на
pg_stat_reset round 2 (Christopher Kings-Lynne)
Список
Дерево обсуждения
pg_stat_reset round 2 "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Re: pg_stat_reset round 2 Neil Conway <nconway@klamath.dyndns.org>
Re: pg_stat_reset round 2 "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
pg_stat_reset round 3 "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Re: pg_stat_reset round 3 Bruce Momjian <pgman@candle.pha.pa.us>
Re: pg_stat_reset round 3 "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Re: pg_stat_reset round 3 Alvaro Herrera <alvherre@atentus.com>
Re: pg_stat_reset round 3 Bruce Momjian <pgman@candle.pha.pa.us>
Re: pg_stat_reset round 3 Bruce Momjian <pgman@candle.pha.pa.us>
"Christopher Kings-Lynne" writes: > This is a reworked patch. It makes pg_stat_reset() a documented builtin > function. It requires superuser privileges to execute. The committer > should check my pg_proc.h entry to make sure I've set isstrict, volatility, > etc. correctly... It should be marked volatile (rather than stable), as it has side-effects. Wouldn't PG_RETURN_VOID() be more appropriate than returning true? Cheers, Neil -- Neil Conway PGP Key ID: DB3C29FC
В списке pgsql-patches по дате отправления
