Обсуждение: LWLockAcquire

Поиск
Список
Период
Сортировка

LWLockAcquire

От
"Gaetano Mendola"
Дата:
Hi all,
this morning I seen on my test linux box ( Postgres 7.2.2) the followin
lines in the logs:

Sep 24 13:49:59 pserver postgres[24943]: [1214174] DEBUG:  BackendStartup:
forked pid=11625 socket=9
Sep 24 13:49:59 pserver postgres[11625]: [1214174] DEBUG:  InitPostgres
Sep 24 13:49:59 pserver postgres[11625]: [1214175] FATAL 1:  Database
"template0" is not currently accepting connections
Sep 24 13:49:59 pserver postgres[11625]: [1214176] DEBUG:  proc_exit(0)
Sep 24 13:49:59 pserver postgres[11625]: [1214177] DEBUG:  shmem_exit(0)
Sep 24 13:49:59 pserver postgres[11625]: [1214178] FATAL 1:  LWLockAcquire:
can't wait without a PROC structure
Sep 24 13:49:59 pserver postgres[11625]: [1214179] DEBUG:  proc_exit(1)
Sep 24 13:49:59 pserver postgres[11625]: [1214180] DEBUG:  shmem_exit(1)
Sep 24 13:49:59 pserver postgres[11625]: [1214181] DEBUG:  exit(1)
Sep 24 13:49:59 pserver postgres[24943]: [1214175] DEBUG:  reaping dead
processes
Sep 24 13:49:59 pserver postgres[24943]: [1214176] DEBUG:  child process
(pid 11625) exited with exit code 1
Sep 24 13:49:59 pserver postgres[24943]: [1214177] DEBUG:  server process
(pid 11625) exited with exit code 1
Sep 24 13:49:59 pserver postgres[24943]: [1214178] DEBUG:  terminating any
other active server processes
Sep 24 13:49:59 pserver postgres[24943]: [1214179] DEBUG:  CleanupProc:
sending SIGQUIT to process 11623
Sep 24 13:49:59 pserver postgres[24943]: [1214180] DEBUG:  CleanupProc:
sending SIGQUIT to process 11609
Sep 24 13:49:59 pserver postgres[11623]: [1214193-1] NOTICE:  Message from
PostgreSQL backend:
Sep 24 13:49:59 pserver postgres[24943]: [1214181] DEBUG:  CleanupProc:
sending SIGQUIT to process 11595
Sep 24 13:49:59 pserver postgres[11609]: [1214157-1] NOTICE:  Message from
PostgreSQL backend:
Sep 24 13:49:59 pserver postgres[11623]: [1214193-2] ^IThe Postmaster has
informed me that some other backend
Sep 24 13:49:59 pserver postgres[24943]: [1214182] DEBUG:  CleanupProc:
sending SIGQUIT to process 11589
Sep 24 13:49:59 pserver postgres[11595]: [1214226-1] NOTICE:  Message from
PostgreSQL backend:
Sep 24 13:49:59 pserver postgres[11609]: [1214157-2] ^IThe Postmaster has
informed me that some other backend
Sep 24 13:49:59 pserver postgres[11623]: [1214193-3] ^Idied abnormally and
possibly corrupted shared memory.
Sep 24 13:49:59 pserver postgres[24943]: [1214183] DEBUG:  CleanupProc:
sending SIGQUIT to process 11584





The machine have 512MB of RAM and
I used for Postgres 128MB of shared memory
shared_buffers=15200
and
max_connections=64


anyone have any idea ?

Ciao
Gaetano

Re: LWLockAcquire

От
Tom Lane
Дата:
"Gaetano Mendola" <mendola@bigfoot.com> writes:
> Sep 24 13:49:59 pserver postgres[11625]: [1214176] DEBUG:  proc_exit(0)
> Sep 24 13:49:59 pserver postgres[11625]: [1214177] DEBUG:  shmem_exit(0)
> Sep 24 13:49:59 pserver postgres[11625]: [1214178] FATAL 1:  LWLockAcquire:
> can't wait without a PROC structure
> Sep 24 13:49:59 pserver postgres[11625]: [1214179] DEBUG:  proc_exit(1)
> Sep 24 13:49:59 pserver postgres[11625]: [1214180] DEBUG:  shmem_exit(1)
> Sep 24 13:49:59 pserver postgres[11625]: [1214181] DEBUG:  exit(1)

Ah-hah!  Thanks for posting that snippet.  I dunno when it would have
occurred to anyone to look for the cause of this message in backend
shutdown, rather than backend startup ... but that was the place to look.

A fix will appear in 7.3 (probably in 7.3beta3).

            regards, tom lane

Re: LWLockAcquire

От
"Gaetano Mendola"
Дата:
"Tom Lane" <tgl@sss.pgh.pa.us> wrote in message
news:10855.1032970976@sss.pgh.pa.us...
>
> Ah-hah!  Thanks for posting that snippet.  I dunno when it would have
> occurred to anyone to look for the cause of this message in backend
> shutdown, rather than backend startup ... but that was the place to look.


You're welcome, but what I should do to avoid this ?
After that message postgres kill all connection running....