Hi!
On 16-12-2009 17:45, Magnus Hagander wrote:
>
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
Thanks, it helps!
Yesterday evening Windows on the server were restarted.
Today the messages still appear, but not so regularly as before.
There wa
On Wed, Dec 16, 2009 at 9:03 PM, Craig Ringer
wrote:
> On 16/12/2009 11:55 PM, Robert Haas wrote:
>>
>> On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander
>> wrote:
>>>
>>> On Wed, Dec 16, 2009 at 16:12, Tom Lane wrote:
Alvaro Herrera writes:
>
> Alexey Luchko wrote:
>>
>>>
On 16/12/2009 11:55 PM, Robert Haas wrote:
On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander wrote:
On Wed, Dec 16, 2009 at 16:12, Tom Lane wrote:
Alvaro Herrera writes:
Alexey Luchko wrote:
postgres.exe!mdpostckpt+0x181b38
postgres.exe!mdpostckpt+0x18bbdb
This stack trace seems bogus.
On Wed, Dec 16, 2009 at 17:43, Alexey Luchko wrote:
> On 16-12-2009 17:45, Magnus Hagander wrote:
>>
>> If that is so, the OP should follow:
>>
>> http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
>>
>> specifically the part about symbols.
>>
>> Which
On 16-12-2009 17:45, Magnus Hagander wrote:
If that is so, the OP should follow:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
specifically the part about symbols.
Which it certainly looks like :)
How can I find the stats collector's process?
On Wed, Dec 16, 2009 at 11:05 AM, Alvaro Herrera
wrote:
> Robert Haas escribió:
>
>> We should really take some of the vast quantity of really useful
>> information that is in the wiki and try to index it somehow or
>> incorporate it into the docs. I'm always learning about new pages
>> that have
Robert Haas escribió:
> We should really take some of the vast quantity of really useful
> information that is in the wiki and try to index it somehow or
> incorporate it into the docs. I'm always learning about new pages
> that have good stuff on them, but I never seem to stumble across them
> o
On Wed, Dec 16, 2009 at 10:45 AM, Magnus Hagander wrote:
> On Wed, Dec 16, 2009 at 16:12, Tom Lane wrote:
>> Alvaro Herrera writes:
>>> Alexey Luchko wrote:
postgres.exe!mdpostckpt+0x181b38
postgres.exe!mdpostckpt+0x18bbdb
>>
>>> This stack trace seems bogus. The stats collector shoul
On Wed, Dec 16, 2009 at 16:12, Tom Lane wrote:
> Alvaro Herrera writes:
>> Alexey Luchko wrote:
>>> postgres.exe!mdpostckpt+0x181b38
>>> postgres.exe!mdpostckpt+0x18bbdb
>
>> This stack trace seems bogus. The stats collector should not be calling
>> mdpostckpt at all.
>
> Given the size of the o
Alvaro Herrera writes:
> Alexey Luchko wrote:
>> postgres.exe!mdpostckpt+0x181b38
>> postgres.exe!mdpostckpt+0x18bbdb
> This stack trace seems bogus. The stats collector should not be calling
> mdpostckpt at all.
Given the size of the offsets, it's pretty clear that it's not actually
in mdpostc
On 16-12-2009 16:28, Alvaro Herrera wrote:
Alexey Luchko wrote:
We've tried to restart the service. It was looking like the service
stopped successfully, but two postgres.exe processes left running.
One of them was utilizing one core. It had no tcp connections in any
state. It was
"C:/Program F
Alexey Luchko wrote:
> We've tried to restart the service. It was looking like the service
> stopped successfully, but two postgres.exe processes left running.
> One of them was utilizing one core. It had no tcp connections in any
> state. It was
> "C:/Program Files/PostgreSQL/8.4/bin/postgres.exe
Hi!
We've got the same issue with PostgreSQL 8.4.1 on 32 bit Windows 2003
Server RC2. Every minute the message "pgstat wait timeout" appears in Event
Viewer / Application Log.
We've tried to restart the service. It was looking like the service stopped
successfully, but two postgres.exe proce
Tom Lane wrote:
Robert Schnabel writes:
From a fresh server restart I have one process that will run one
processor 100% essentially forever. (I've let it go for about a week
just to see if it would ever stop and it didn't). Attached is a text
dump from ProcessExplorer. I h
Robert Schnabel writes:
> From a fresh server restart I have one process that will run one
> processor 100% essentially forever. (I've let it go for about a week
> just to see if it would ever stop and it didn't). Attached is a text
> dump from ProcessExplorer. I have highlighted the releva
I've been having an issue for about 5 months now and after upgrading to
8.4 did not fix it I figured I'd try this list. I tried the perform
list a while back but no bites.
My system: Windows XP64 SP2, dual Opteron 2218, 12G ram, PostgreSQL
8.4. I am the only person using the postgres server
16 matches
Mail list logo
