Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 5C0F29FB4E2 for ; Fri, 23 Mar 2007 20:38:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 27036-05 for ; Fri, 23 Mar 2007 20:38:05 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from actenon.computec.com.co (actenon.computec.com.co [200.74.143.146]) by postgresql.org (Postfix) with SMTP id 47FCB9FB436 for ; Fri, 23 Mar 2007 20:38:09 -0300 (ADT) Received: from computecnew.redcorp.computec.com ([172.24.10.109]) by actenon.computec.com.co (SMSSMTP 4.1.11.41) with SMTP id M2007032318364725152 for ; Fri, 23 Mar 2007 18:36:47 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C76DA4.496EBE90" Subject: AYUDA URGENTE CON TABLA PG_SHADOW Date: Fri, 23 Mar 2007 18:37:57 -0500 Message-ID: <873F3E256E0BF14EA84EAC54C2886B5D0B9830@computecnew.redcorp.computec.com> In-Reply-To: <63EA6DBE-34B9-4D2D-A61C-D7EF38B3D9DB@MeridiasCapital.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AYUDA URGENTE CON TABLA PG_SHADOW Thread-Index: AcdtoX0MR9477drfSQe1QrUwT2376QAAp5LA From: "Daniel Ricardo Medina" To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.687 tagged_above=0 required=5 tests=AWL, BAYES_50, HTML_30_40, HTML_MESSAGE, SUBJ_ALL_CAPS X-Spam-Level: X-Archive-Number: 200703/180 X-Sequence-Number: 25004 This is a multi-part message in MIME format. ------_=_NextPart_001_01C76DA4.496EBE90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ayuda por favor Cuando ejecuto este comando me sale una doble tupla del usuario postgres, esto me error cuando ejecuto el comando Pg_dump para realizar el respectivo backup.. =20 radar=3D# select * from pg_user; usename | usesysid | usecreatedb | usesuper | usecatupd | passwd | valuntil | useconfig -----------+----------+-------------+----------+-----------+----------+- ---------+----------- postgres | 1 | t | t | t | ******** | | postgres | 1 | t | t | t | ******** | | userradar | 100 | f | f | f | ******** | | (3 rows) He intentado borrar los usuario directamente de la tabla subiendo postgres com postgres -O -P -D directorio Y corriendo estos comandos.. select * from pg_shadow; delete from pg_shadow; CREATE USER postgres WITH CREATEDB CREATEUSER PASSWORD '***' SYSID 1; CREATE USER userradar PASSWORD '***'=20 Pero me crea los mismos tres usuarios en la tabla pg_shadow, el problema es que no he podido hacer el backup y ya no tengo espacio en la particion donde tengo montada la base =20 =20 =20 =20 =20 =20 Ayuda por favor Cuando ejecuto este comando me sale una doble tupla del usuario postgres, esto me error cuando ejecuto el comando Pg_dump para realizar el respectivo backup.. =20 radar=3D# select * from pg_user; usename | usesysid | usecreatedb | usesuper | usecatupd | passwd | valuntil | useconfig -----------+----------+-------------+----------+-----------+----------+- ---------+----------- postgres | 1 | t | t | t | ******** | | postgres | 1 | t | t | t | ******** | | userradar | 100 | f | f | f | ******** | | (3 rows) He intentado borrar los usuario directamente de la tabla subiendo postgres com postgres -O -P -D directorio Y corriendo estos comandos.. select * from pg_shadow; delete from pg_shadow; CREATE USER postgres WITH CREATEDB CREATEUSER PASSWORD '***' SYSID 1; CREATE USER userradar PASSWORD '***'=20 Pero me crea los mismos tres usuarios en la tabla pg_shadow, el problema es que no he podido hacer el backup y ya no tengo espacio en la particion donde tengo montada la base =20 =20 =20 =20 =20 =20 Daniel Ricardo Medina Ing. de Desarrollo Computec S.A. Tel 260 71 11 Ext 1640 =20 ________________________________ De: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] En nombre de Warren Little Enviado el: Friday, March 23, 2007 6:16 PM Para: pgsql-admin@postgresql.org Asunto: [ADMIN] trying to run PITR recovery Hello, I'm testing my PITR recovery procedures and something doesn't look right. The following is from the logs upon starting postgres with recovery.conf file in place 2007-03-23 05:56:00 MDTLOG: database system was interrupted at 2007-03-18 05:09:15 MDT @ 2007-03-23 05:56:00 MDTLOG: starting archive recovery @ 2007-03-23 05:56:00 MDTLOG: restore_command =3D "cp /data/pgLocal/archive/WAL_restore/%f "%p"" cp: cannot stat `/data/pgLocal/archive/WAL_restore/00000001.history': No such file or directory @ 2007-03-23 05:56:00 MDTLOG: restored log file "000000010000011A000000EE.004E0060.backup" from archive @ 2007-03-23 05:56:00 MDTLOG: restored log file "000000010000011A000000EE" from archive @ 2007-03-23 05:56:00 MDTLOG: checkpoint record is at 11A/EE4E0060 @ 2007-03-23 05:56:00 MDTLOG: redo record is at 11A/EE4E0060; undo record is at 0/0; shutdown FALSE @ 2007-03-23 05:56:00 MDTLOG: next transaction ID: 2415965426; next OID: 81701223 @ 2007-03-23 05:56:00 MDTLOG: next MultiXactId: 43380; next MultiXactOffset: 92368 @ 2007-03-23 05:56:00 MDTLOG: automatic recovery in progress @ 2007-03-23 05:56:01 MDTLOG: redo starts at 11A/EE4E00B0 @ 2007-03-23 05:56:15 MDTLOG: restored log file "000000010000011A000000EF" from archive @ 2007-03-23 05:56:27 MDTLOG: restored log file "000000010000011A000000F0" from archive @ 2007-03-23 05:56:31 MDTLOG: restored log file "000000010000011A000000F1" from archive @ 2007-03-23 05:56:34 MDTLOG: restored log file "000000010000011A000000F2" from archive @ 2007-03-23 05:56:40 MDTLOG: restored log file "000000010000011A000000F3" from archive @ 2007-03-23 05:56:50 MDTLOG: restored log file "000000010000011A000000F4" from archive @ 2007-03-23 05:57:02 MDTLOG: restored log file "000000010000011A000000F5" from archive @ 2007-03-23 05:57:07 MDTLOG: restored log file "000000010000011A000000F6" from archive @ 2007-03-23 05:57:11 MDTLOG: restored log file "000000010000011A000000F7" from archive @ 2007-03-23 05:57:14 MDTLOG: restored log file "000000010000011A000000F8" from archive @ 2007-03-23 05:57:18 MDTLOG: restored log file "000000010000011A000000F9" from archive @ 2007-03-23 05:57:21 MDTLOG: restored log file "000000010000011A000000FA" from archive @ 2007-03-23 05:57:27 MDTLOG: restored log file "000000010000011A000000FB" from archive @ 2007-03-23 05:57:29 MDTLOG: restored log file "000000010000011A000000FC" from archive @ 2007-03-23 05:57:33 MDTLOG: restored log file "000000010000011A000000FD" from archive @ 2007-03-23 05:57:35 MDTLOG: incorrect resource manager data checksum in record at 11A/FD492B20 @ 2007-03-23 05:57:35 MDTLOG: redo done at 11A/FD492210 @ 2007-03-23 05:57:36 MDTLOG: restored log file "000000010000011A000000FD" from archive @ 2007-03-23 05:57:36 MDTLOG: archive recovery complete @ 2007-03-23 05:57:36 MDTLOG: could not truncate directory "pg_multixact/members": apparent wraparound @ 2007-03-23 05:59:00 MDTLOG: database system is ready @ 2007-03-23 05:59:00 MDTLOG: transaction ID wrap limit is 3065701724, limited by database "postgres" @ 2007-03-23 12:14:04 MDTLOG: autovacuum: processing database "postgres" My concern is that there were many more logfiles to be played following "00000010000011A000000FD"=20 (ie 000000010000011E0000005C) yet it appears the recovery stop at that point and called it good. I would assume all WAL logs would be restored. The recovery.conf was simple:=20 restore_command =3D 'cp /data/pgLocal/archive/WAL_restore/%f "%p"' The backup file 000000010000011A000000EE.004E0060.backup" contained: START WAL LOCATION: 11A/EE4E0060 (file 000000010000011A000000EE) STOP WAL LOCATION: 11A/EFF68AB8 (file 000000010000011A000000EF) CHECKPOINT LOCATION: 11A/EE4E0060 START TIME: 2007-03-17 20:29:16 MDT LABEL: 076_pgdata.tar STOP TIME: 2007-03-18 05:16:17 MDT Does the line: incorrect resource manager data checksum in record at 11A/FD492B20 mean there is a corrupted WAL log file? Any insight here would be helpful=20 version PG 8.1.2 64 bit Linux thanks Warren Little Chief Technology Officer Meridias Capital Inc ph 866.369.7763 ------_=_NextPart_001_01C76DA4.496EBE90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Ayuda por favor

Cuando ejecuto este comando me sale una doble tupla del usuario = postgres,=20 esto me error cuando ejecuto el comando Pg_dump para realizar el = respectivo=20 backup..

 

radar=3D# select * from pg_user;

usename | usesysid | usecreatedb | usesuper | usecatupd | passwd | = valuntil |=20 useconfig

-----------+----------+-------------+----------+-----------+----------= +----------+-----------

postgres | 1 | t | t | t | ******** | |

postgres | 1 | t | t | t | ******** | |

userradar | 100 | f | f | f | ******** | |

(3 rows)

He intentado borrar los usuario directamente de la tabla subiendo = postgres=20 com postgres -O -P -D directorio

Y corriendo estos comandos..

select * from pg_shadow;

delete from pg_shadow;

CREATE USER postgres WITH CREATEDB CREATEUSER PASSWORD '***' SYSID 1; = CREATE=20 USER userradar PASSWORD '***'

Pero me crea los mismos tres usuarios en la tabla pg_shadow, el = problema es=20 que no he podido hacer el backup y ya no tengo espacio en la particion = donde=20 tengo montada la base

 

 

 

 

 

 

Ayuda por favor

Cuando ejecuto este comando me sale una doble tupla del usuario = postgres,=20 esto me error cuando ejecuto el comando Pg_dump para realizar el = respectivo=20 backup..

 

radar=3D# select * from pg_user;

usename | usesysid | usecreatedb | usesuper | usecatupd | passwd | = valuntil |=20 useconfig

-----------+----------+-------------+----------+-----------+----------= +----------+-----------

postgres | 1 | t | t | t | ******** | |

postgres | 1 | t | t | t | ******** | |

userradar | 100 | f | f | f | ******** | |

(3 rows)

He intentado borrar los usuario directamente de la tabla subiendo = postgres=20 com postgres -O -P -D directorio

Y corriendo estos comandos..

select * from pg_shadow;

delete from pg_shadow;

CREATE USER postgres WITH CREATEDB CREATEUSER PASSWORD '***' SYSID 1; = CREATE=20 USER userradar PASSWORD '***'

Pero me crea los mismos tres usuarios en la tabla pg_shadow, el = problema es=20 que no he podido hacer el backup y ya no tengo espacio en la particion = donde=20 tengo montada la base

 

 

 

 

 

 
Daniel Ricardo=20 Medina
Ing. de=20 Desarrollo
Computec=20 S.A.
Tel 260 71 11=20 Ext 1640
 


De: pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] En nombre de Warren=20 Little
Enviado el: Friday, March 23, 2007 6:16 = PM
Para:=20 pgsql-admin@postgresql.org
Asunto: [ADMIN] trying to run PITR=20 recovery

Hello,
I'm testing my PITR recovery procedures and something doesn't look=20 right.
The following is from the logs upon starting postgres with = recovery.conf=20 file in place

 2007-03-23 05:56:00 MDTLOG:  database system was = interrupted at=20 2007-03-18 05:09:15 MDT
@ 2007-03-23 05:56:00 MDTLOG:  starting archive recovery
@ 2007-03-23 05:56:00 MDTLOG:  restore_command =3D "cp=20 /data/pgLocal/archive/WAL_restore/%f "%p""
cp: cannot stat = `/data/pgLocal/archive/WAL_restore/00000001.history': No=20 such file or directory
@ 2007-03-23 05:56:00 MDTLOG:  restored log file=20 "000000010000011A000000EE.004E0060.backup" from archive
@ 2007-03-23 05:56:00 MDTLOG:  restored log file=20 "000000010000011A000000EE" from archive
@ 2007-03-23 05:56:00 MDTLOG:  checkpoint record is at=20 11A/EE4E0060
@ 2007-03-23 05:56:00 MDTLOG:  redo record is at 11A/EE4E0060; = undo=20 record is at 0/0; shutdown FALSE
@ 2007-03-23 05:56:00 MDTLOG:  next transaction ID: = 2415965426; next=20 OID: 81701223
@ 2007-03-23 05:56:00 MDTLOG:  next MultiXactId: 43380; next=20 MultiXactOffset: 92368
@ 2007-03-23 05:56:00 MDTLOG:  automatic recovery in = progress
@ 2007-03-23 05:56:01 MDTLOG:  redo starts at = 11A/EE4E00B0
@ 2007-03-23 05:56:15 MDTLOG:  restored log file=20 "000000010000011A000000EF" from archive
@ 2007-03-23 05:56:27 MDTLOG:  restored log file=20 "000000010000011A000000F0" from archive
@ 2007-03-23 05:56:31 MDTLOG:  restored log file=20 "000000010000011A000000F1" from archive
@ 2007-03-23 05:56:34 MDTLOG:  restored log file=20 "000000010000011A000000F2" from archive
@ 2007-03-23 05:56:40 MDTLOG:  restored log file=20 "000000010000011A000000F3" from archive
@ 2007-03-23 05:56:50 MDTLOG:  restored log file=20 "000000010000011A000000F4" from archive
@ 2007-03-23 05:57:02 MDTLOG:  restored log file=20 "000000010000011A000000F5" from archive
@ 2007-03-23 05:57:07 MDTLOG:  restored log file=20 "000000010000011A000000F6" from archive
@ 2007-03-23 05:57:11 MDTLOG:  restored log file=20 "000000010000011A000000F7" from archive
@ 2007-03-23 05:57:14 MDTLOG:  restored log file=20 "000000010000011A000000F8" from archive
@ 2007-03-23 05:57:18 MDTLOG:  restored log file=20 "000000010000011A000000F9" from archive
@ 2007-03-23 05:57:21 MDTLOG:  restored log file=20 "000000010000011A000000FA" from archive
@ 2007-03-23 05:57:27 MDTLOG:  restored log file=20 "000000010000011A000000FB" from archive
@ 2007-03-23 05:57:29 MDTLOG:  restored log file=20 "000000010000011A000000FC" from archive
@ 2007-03-23 05:57:33 MDTLOG:  restored log file=20 "000000010000011A000000FD" from archive
@ 2007-03-23 05:57:35 MDTLOG:  incorrect resource manager data = checksum in record at 11A/FD492B20
@ 2007-03-23 05:57:35 MDTLOG:  redo done at 11A/FD492210
@ 2007-03-23 05:57:36 MDTLOG:  restored log file=20 "000000010000011A000000FD" from archive
@ 2007-03-23 05:57:36 MDTLOG:  archive recovery complete
@ 2007-03-23 05:57:36 MDTLOG:  could not truncate directory=20 "pg_multixact/members": apparent wraparound
@ 2007-03-23 05:59:00 MDTLOG:  database system is ready
@ 2007-03-23 05:59:00 MDTLOG:  transaction ID wrap limit is=20 3065701724, limited by database "postgres"
@ 2007-03-23 12:14:04 MDTLOG:  autovacuum: processing database = "postgres"

My concern is that there were many more logfiles to be played = following=20 "00000010000011A000000FD" 
(ie 000000010000011E0000005C) yet it appears the recovery = stop at=20 that point and called it good.
I would assume all WAL logs would be restored.

The recovery.conf was simple: 
restore_command =3D 'cp /data/pgLocal/archive/WAL_restore/%f = "%p"'

The backup file 000000010000011A000000EE.004E0060.backup"=20 contained:
START WAL LOCATION: 11A/EE4E0060 (file = 000000010000011A000000EE)
STOP WAL LOCATION: 11A/EFF68AB8 (file = 000000010000011A000000EF)
CHECKPOINT LOCATION: 11A/EE4E0060
START TIME: 2007-03-17 20:29:16 MDT
LABEL: 076_pgdata.tar
STOP TIME: 2007-03-18 05:16:17 MDT

Does the line:  incorrect resource manager data checksum = in=20 record at 11A/FD492B20
mean there is a corrupted WAL log file?

Any insight here would be helpful 
version PG 8.1.2 64 bit Linux


thanks


Warren Little
Chief Technology Officer
Meridias Capital Inc
ph 866.369.7763


------_=_NextPart_001_01C76DA4.496EBE90--