LinkedIn
Fernando Machado requested to add you as a connection on LinkedIn:
--
Arthur,
Eu gostaria de adicioná-lo à minha rede profissional no LinkedIn.
-Fernando
Accept invitation from Fernando Machado
Hi,
I'm trying to understand the information shown in pg_stat_bgwriter.
If I want to identify a possible bottleneck with the bgwriter, for what kind of
numbers do I need to watch out?
Are the following values OK, or do they indicate that I need to tune my
configuration?
checkpoints_timed :
Thomas Kellerer wrote:
If I want to identify a possible bottleneck with the bgwriter, for
what kind of numbers do I need to watch out?
You don't much with a single snapshot of pg_stat_bgwriter data. Try
saving this instead:
select *,now() from pg_stat_bgwriter;
And then take another
Greg Smith wrote on 08.06.2010 19:30:
Thomas Kellerer wrote:
If I want to identify a possible bottleneck with the bgwriter, for
what kind of numbers do I need to watch out?
You don't much with a single snapshot of pg_stat_bgwriter data. Try
saving this instead:
select *,now() from
I am looking for some specific information regarding optimizer behavior.
We recently experienced a situation where a query that was previously using a
btree lookup (efficient) SWITCHED to using seqscan/hash lookup.
My questions would be:
- Under what circumstances is the optimizer
Greg Smith wrote:
You don't much with a single snapshot of pg_stat_bgwriter data. Try
saving this instead:
select *,now() from pg_stat_bgwriter;
And then take another snapshot at least a few hours later, preferably
the next day. With two snapshots and timestamps on them, then it's
possible
On Tue, Jun 8, 2010 at 8:58 PM, Mark Rostron mrost...@ql2.com wrote:
I am looking for some specific information regarding optimizer behavior.
We recently experienced a situation where a query that was previously using
a btree lookup (efficient) SWITCHED to using seqscan/hash lookup.
OK,
