Обсуждение: Execute vacuum postgresql crash

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

Execute vacuum postgresql crash

От
"frank_lupo"
Дата:
When execute a vacuum postgresql crash.
The table examinate have a 161372 record.
I execute a 'vacuum full irtab\g'


DEBUG:  --Relation irtab--
DEBUG:  Pages 11235: Changed 0, reaped 5630, Empty 0, New 0; Tup
161372: Vac 8,
Keep/VTL 0/0, UnUsed 161372, MinLen 56, MaxLen 440; Re-using:
Free/Avail. Space
45905892/45872300; EndEmpty/Avail. Pages 0/9933.
        CPU 0.20s/0.06u sec elapsed 0.25 sec.
DEBUG:  Index irtab_id: Pages 445; Tuples 161372: Deleted 8.
        CPU 0.01s/0.08u sec elapsed 0.29 sec.
DEBUG:  Index irtab_pad: Pages 445; Tuples 161372: Deleted 8.
        CPU 0.00s/0.10u sec elapsed 0.30 sec.
DEBUG:  Index irtab_cod: Pages 847; Tuples 161372: Deleted 8.
        CPU 0.06s/0.06u sec elapsed 0.50 sec.
DEBUG:  Index irtab_codunic_vis: Pages 445; Tuples 161372: Deleted 8.
        CPU 0.02s/0.06u sec elapsed 0.27 sec.
DEBUG:  Index irtab_nom_var: Pages 446; Tuples 161372: Deleted 8.
        CPU 0.00s/0.06u sec elapsed 0.28 sec.
DEBUG:  Index irtab_sys_var: Pages 445; Tuples 161372: Deleted 8.
        CPU 0.00s/0.06u sec elapsed 0.30 sec.
DEBUG:  Index irtab_ris: Pages 445; Tuples 161372: Deleted 8.
        CPU 0.02s/0.11u sec elapsed 0.32 sec.
DEBUG:  Index irtab_codunic: Pages 446; Tuples 161372: Deleted 8.
        CPU 0.01s/0.10u sec elapsed 0.33 sec.
DEBUG:  recycled transaction log file 0000000100000068
DEBUG:  recycled transaction log file 0000000100000069
DEBUG:  recycled transaction log file 000000010000006A
FATAL 2:  link from /usr/share/postgresql/data/pg_xlog/0000000100000068
to /usr/
share/postgresql/data/pg_xlog/0000000100000073 (initialization of log
file 1, se
gment 115) failed: Permission denied
DEBUG:  server process (pid 1828) exited with exit code 2
DEBUG:  terminating any other active server processes
NOTICE:  Message from PostgreSQL backend:NOTICE:  Message from
PostgreSQL backen
d:NOTICE:  Message from PostgreSQL backend:NOTICE:  Message from
PostgreSQL back
end:



        The Postmaster has informed me that some other backend
The Postmaster has informed me that some other backend
The Postmaster has informed me that some other backend

        died abnormally and possibly corrupted shared memory.   died
abnormally
and possibly corrupted shared memory.   died abnormally and possibly
corrupted s
hared medied abnormally and possibly corrupted shared memory.



        I have rolled back the current transaction and am
I have rolled back the current transaction and am
I have rolled back the current transaction and am

        going to terminate your database system connection and exit.
going to
 terminate your database system connection and exit.    going to
terminate your
databasegoing to terminate your database system connection and exit.



        Please reconnect to the database system and repeat your query.
Please reconnect to the database system and repeat your query.
Please reconnect to the database system and repeat your query.

NOTICE:  Message from PostgreSQL backend:
        The Postmaster has informed me that some other backend
        died abnormally and possibly corrupted shared memory.
        I have rolled back the current transaction and am
        going to terminate your database system connection and exit.
        Please reconnect to the database system and repeat your query.
NOTICE:  Message from PostgreSQL backend:
        The Postmaster has informed me that some other backend
        died abnormally and possibly corrupted shared memory.
        I have rolled back the current transaction and am
        going to terminate your database system connection and exit.
        Please reconnect to the database system and repeat your query.
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: DEBUG:  all
server proc
esses terminated; reinitializing shared memory and semaphores
IpcMemoryCreate: shmget(key=5432001, size=1441792, 03600) failed: Not
enough mem
ory

This error usually means that PostgreSQL's request for a shared
memory segment exceeded available memory or swap space.
To reduce the request size (currently 1441792 bytes), reduce
PostgreSQL's shared_buffers parameter (currently 64) and/or
its max_connections parameter (currently 32).

The PostgreSQL Administrator's Guide contains more information about
shared memory configuration.

Failed.
!#
!#


Bye !!
Frank Lupo (Wolf) !!



--
Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f

Sponsor:
Sai cosa � una "lampada di sale"? scoprilo qui:
Clicca qui: http://adv2.email.it/cgi-bin/foclick.cgi?mid=373&d=26-7

Re: Execute vacuum postgresql crash

От
Tom Lane
Дата:
"frank_lupo" <frank_lupo@email.it> writes:
> FATAL 2:  link from /usr/share/postgresql/data/pg_xlog/0000000100000068
> to /usr/
> share/postgresql/data/pg_xlog/0000000100000073 (initialization of log
> file 1, se
> gment 115) failed: Permission denied

"Permission denied"?  What have you done to the ownership/permissions
of pg_xlog/ and the files in it?

            regards, tom lane

Re: Execute vacuum postgresql crash

От
"frank_lupo"
Дата:
> "frank_lupo" <frank_lupo@email.it> writes:
> > FATAL 2:  link
from /usr/share/postgresql/data/pg_xlog/0000000100000068
> > to /usr/
> > share/postgresql/data/pg_xlog/0000000100000073 (initialization of
log
> > file 1, se
> > gment 115) failed: Permission denied
>
> "Permission denied"?  What have you done to the ownership/permissions
> of pg_xlog/ and the files in it?
>
>             regards, tom lane
>

gedis30=# vacuum full;
NOTICE:  Message from PostgreSQL backend:
        The Postmaster has informed me that some other backend
        died abnormally and possibly corrupted shared memory.
        I have rolled back the current transaction and am
        going to terminate your database system connection and exit.
        Please reconnect to the database system and repeat your query.
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!#
!#
!#
!#

Thank

Bye !!
Frank Lupo (Wolf) !!



--
Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f

Sponsor:
Email.it Free (Internet) Access
Prova il Nuovo Numero Unico valido per tutta Italia a tariffa locale!!!
Email.it Free Access, dai pi� qualit� alla tua navigazione....
Clicca qui: http://adv2.email.it/cgi-bin/foclick.cgi?mid=441&d=30-7