Skip site navigation (1) Skip section navigation (2)

Re: keeping a timestamp of the last stats reset (for a db, table and function)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: keeping a timestamp of the last stats reset (for a db, table and function)
Date: 2010-12-19 23:03:30
Message-ID: 17858.1292799810@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
I wrote:
> That is not the number of interest.  The number of interest is that it's
> 8 bytes added onto a struct that currently contains 11 of 'em; in other
> words a 9% increase in the size of the stats file, and consequently
> about a 9% increase in the cost of updating it.

Wups, sorry, I was looking at the wrong struct.  It's actually an
addition of 1 doubleword to a struct of 21 of 'em, or about 5%.
That's still an awful lot in comparison to the prospective usefulness
of the information.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Itagaki TakahiroDate: 2010-12-20 00:03:56
Subject: Re: Extensions, patch v20 (bitrot fixes)
Previous:From: Tom LaneDate: 2010-12-19 22:58:11
Subject: Re: keeping a timestamp of the last stats reset (for a db, table and function)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group