> However, I disagree with resetting last_autovac_time ... that's not a
> counter, so there's no particularly good reason to discard its value.
Oh yeah, I see. Haven't realized that when writing the patch.
regards
Tomas
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make ch
After calling pg_stat_reset, some of the database stats fields are not
actually reset, the value is preserved. I've found the bug is actually in
pgstat_recv_resetcounter function, where only some of the
PgStat_StatDBEntry fields are reset to 0.
This is true for those 6 fields:
n_tuples_returned
n
Hi,
one of my colleagues found ugly memory leak in the xml2 contrib module.
Try this:
select xpath_number('' || generate_series || '','/data') from
generate_series(1,50);
This will allocate arbitrary amount of memory, and it won't release it
until the backend exits (user disconnects). We've
