From: | Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com> |
---|---|
To: | Gabriel Ferro <gabrielrferro(at)yahoo(dot)com(dot)ar>, pgsql-es-ayuda <pgsql-es-ayuda(at)postgresql(dot)org> |
Subject: | Re: Error en vacuum antes era error con update |
Date: | 2009-03-11 12:23:50 |
Message-ID: | f205bb120903110523s3a7c127fl26988ee88739e054@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda |
2009/3/11 Gabriel Ferro <gabrielrferro(at)yahoo(dot)com(dot)ar>:
>
> uuuuuuhhhyy... hice REINDEX DATABASE
> reindexa varias tablas y en un momento aparece
> ERROR: invalid memory alloc request size 1279336523
> si pierdo los datos me mato.... estuve 2 semanas cargando.....
> que hago?, reinstalo postgres? o es un problema de configuracion=?
> por ejemplo a fsync lo tengo comentado, les paso algunas configuraciones que tengo
>
> listen_addresses ='*'
> port = 5432 # (change requires restart)
> max_connections = 100 # (change requires restart)
> unix_socket_directory = '/var/run/postgresql' # (change requires restart)
> authentication_timeout = 1min # 1s-600s
> password_encryption = on
> shared_buffers = 24MB # ORIG ES 24 min 128kB or max_connections*16kB 16
> #temp_buffers = 8MB # min 800kB
> #max_prepared_transactions = 5 # can be 0 or more
> #work_mem = 8MB # ORIG COMENTADO min 64kB
> #maintenance_work_mem = 256MB # ORIG sin comentar min 1MB
> #max_stack_depth = 2MB # min 100kB
> # - Free Space Map -
> #max_fsm_pages = 153600 # min max_fsm_relations*16, 6 bytes each
> #max_fsm_pages = 2159795
> #max_fsm_pages = 320000
> max_fsm_pages = 608048
> #fsync = on # turns forced synchronization on or off
> #synchronous_commit = on # immediate fsync at commit
> #debug_print_parse = off
> #debug_print_rewritten = off
> #debug_print_plan = off
> #debug_pretty_print = off
> #log_checkpoints = off
> #log_connections = off
> #log_disconnections = off
> #log_duration = off
> #log_hostname = off
> log_line_prefix = '%t '
> autovacuum = on # ORIG comentado Enable autovacuum subprocess? 'on'
> datestyle = 'iso, dmy'
> lc_messages = 'es_AR.UTF-8' # locale for system error message
>
> lc_monetary = 'es_AR.UTF-8' # locale for monetary formatting
> lc_numeric = 'es_AR.UTF-8' # locale for number formatting
> lc_time = 'es_AR.UTF-8' # locale for time formatting
> default_text_search_config = 'pg_catalog.spanish'
>
>
> Yahoo! Cocina
> Recetas prácticas y comida saludable
> http://ar.mujer.yahoo.com/cocina/
> --
> TIP 1: para suscribirte y desuscribirte, visita http://archives.postgresql.org/pgsql-es-ayuda
>
No creo que sea de configuración.
Corriste Vacuum analyze? Con eso debería solucionarse.
Threads interesantes:
http://archives.postgresql.org//pgsql-bugs/2006-03/msg00193.php
http://archives.postgresql.org/pgsql-bugs/2006-03/msg00197.php
http://archives.postgresql.org/pgsql-committers/2006-03/msg00094.php
Esto fue patcheado anteriormente. Creo que al hacer reindex a los
catalogos salto esto.
--
Emanuel Calvo Franco
Sumate al ARPUG !
(www.postgres-arg.org -
www.arpug.com.ar)
ArPUG / AOSUG Member
Postgresql Support & Admin
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-03-11 13:39:31 | Re: Ingeniería inversa sobre BD existente |
Previous Message | Alvaro Herrera | 2009-03-11 12:22:54 | Re: Error en vacuum antes era error con update |