Jeff Janes writes:
> On Wed, Mar 12, 2014 at 7:42 AM, Tom Lane wrote:
>> We've seen sporadic reports of that sort of behavior for years, but no
>> developer has ever been able to reproduce it reliably. Now that you've
>> got a reproducible case, do you want to poke into it and see what's going
>
On Wed, Mar 12, 2014 at 7:42 AM, Tom Lane wrote:
> Kouhei Kaigai writes:
> > WARNING: pgstat wait timeout
> > WARNING: pgstat wait timeout
> > WARNING: pgstat wait timeout
> > WARNING: pgstat wait timeout
>
> > Once I got above messages, write performance is dramatically
> > degraded, even t
On 12 Březen 2014, 14:54, Kouhei Kaigai wrote:
> It is another topic from the main thread,
>
> I noticed the following message under the test cases that
> takes heavy INSERT workload; provided by Haribabu.
>
> [kaigai@iwashi ~]$ createdb mytest
> [kaigai@iwashi ~]$ psql -af ~/cache_scan.sql mytest
Kouhei Kaigai writes:
> WARNING: pgstat wait timeout
> WARNING: pgstat wait timeout
> WARNING: pgstat wait timeout
> WARNING: pgstat wait timeout
> Once I got above messages, write performance is dramatically
> degraded, even though I didn't take detailed investigation.
> I could reproduce i
It is another topic from the main thread,
I noticed the following message under the test cases that
takes heavy INSERT workload; provided by Haribabu.
[kaigai@iwashi ~]$ createdb mytest
[kaigai@iwashi ~]$ psql -af ~/cache_scan.sql mytest
\timing
Timing is on.
--cache scan select 5 million
create
