Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id B65182E0076 for ; Fri, 9 May 2008 16:49:19 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 02402-05 for ; Fri, 9 May 2008 16:49:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by developer.postgresql.org (Postfix) with ESMTP id C2AEC2E0067 for ; Fri, 9 May 2008 16:49:07 -0300 (ADT) Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m49JmFRg009043; Fri, 9 May 2008 14:49:01 -0500 (CDT) Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 May 2008 14:48:41 -0500 Received: from DEEXC1U03.de.lucent.com ([135.248.187.20]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 May 2008 21:48:39 +0200 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_01C8B20D.ACEF228F" Subject: Re: debug issue on postgresql Date: Fri, 9 May 2008 21:48:35 +0200 Message-ID: <85618CB6B1C0F14D888609DB41641AB40127F290@DEEXC1U03.de.lucent.com> In-Reply-To: <4824841F.4020104@lelarge.info> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] debug issue on postgresql Thread-Index: Acix9selwAk56dyTSyqVpL2TfHBDIgAEexYg References: <85618CB6B1C0F14D888609DB41641AB40127F1EA@DEEXC1U03.de.lucent.com> <4824841F.4020104@lelarge.info> From: "MARIOTTI, Alessandro \(Alessandro\)" To: "Guillaume Lelarge" Cc: X-OriginalArrivalTime: 09 May 2008 19:48:39.0247 (UTC) FILETIME=[AD55F5F0:01C8B20D] X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200805/84 X-Sequence-Number: 29168 This is a multi-part message in MIME format. ------_=_NextPart_001_01C8B20D.ACEF228F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Guillaume, =20 Well I could shortly describe what's happen on these machines ; =20 On May 7 2008 at 23:25 an operator performed : _a configuration change ; _add a new user on a table named MVNO; Customer told us that for "new user" operator add comma "," symbol. This is something new for their provisioning procedure (it's seems they = never test it )thus as soon as they propagate this updated DB over = machines of live net these started to discard all the requests and no = more user was able to work or work properly . =20 Now they asking us what's happen so this is the reason why I'm writing = here . =20 Unfortunately I tried to verify the backup db but the one interesting = for us is empty : =20 ls -l 200805* -rw-r--r-- 1 root root 842840 mag 1 04:03 = 20080501-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 842840 mag 2 04:03 = 20080502-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 842840 mag 3 04:03 = 20080503-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 842840 mag 4 04:03 = 20080504-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 842540 mag 5 04:03 = 20080505-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 842613 mag 6 04:03 = 20080506-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 842613 mag 7 04:03 = 20080507-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 0 mag 8 04:03 = 20080508-0403-cfg_xxxxxxx.sql -rw-r--r-- 1 root root 843960 mag 9 04:03 = 20080509-0403-cfg_xxxxxxx.sql =20 =20 I'll try to find it but but even if I can't provide this back-up for = company policies reason , could I ask you some feed-back to get = suggestion to look for on this back-up file? =20 Many thanx anyway for your help =20 Best Regards =20 Alessandro. =20 =20 -----Original Message----- From: Guillaume Lelarge [mailto:guillaume@lelarge.info]=20 Sent: venerd=EC 9 maggio 2008 19:05 To: MARIOTTI, Alessandro (Alessandro) Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] debug issue on postgresql =20 MARIOTTI, Alessandro (Alessandro) a =E9crit : > I'm writing you to get some information regarding the possibility to = get=20 > some information a db corruption got yesterday morning in a live = platform . >=20 > We realized DB Inconsistence and corruption and we tried to restore=20 > immediately the DB , via a back-up procedure, to restore services for=20 > customer. >=20 > Now we need to investigate on DB what it was the route cause for db=20 > corruption. >=20 =20 Do you have a backup of the corrupted database ? If you don't, it will=20 be extremely hard to tell you anything interesting. =20 And you need to tell us what kind of issue you have, which release you=20 use, etc. =20 > Unfortunately we don't have any experience with postgres db because = the=20 > platform had improved by a colleague that left company and no one got=20 > the opportunity to learn something ..... >=20 > Some documentation to start with postgres will be appreciate . >=20 =20 http://www.postgresql.org/docs/ and then choose the manual related to=20 your PostgreSQL release. =20 Regards. =20 =20 --=20 Guillaume. http://www.postgresqlfr.org http://dalibo.com ------_=_NextPart_001_01C8B20D.ACEF228F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Guillaume,

 

Well I could shortly describe what's happen on these machines = ;

 

On May 7 2008 at 23:25 an operator performed = :

_a configuration change ;

_add a new user on a table named = MVNO;

Customer told us that for =A0“new user” operator add = comma “,” symbol.

This is something new for their provisioning procedure = (it’s seems they never test it )thus as soon as they propagate this updated DB = over machines of live net these started to discard all the requests and no more user = was able to work or work properly .

 

Now they asking us what’s happen so this is the reason why = I’m writing here .

 

Unfortunately I tried to verify the backup db but the one = interesting for us is empty :

 

ls -l=A0 200805*

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 842840 mag=A0 1 04:03 20080501-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 842840 mag=A0 2 04:03 20080502-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 842840 mag=A0 3 04:03 20080503-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 842840 mag=A0 4 04:03 20080504-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 842540 mag=A0 5 04:03 20080505-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 842613 mag=A0 6 04:03 20080506-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 842613 mag=A0 7 04:03 20080507-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 = root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 0 mag=A0 8 04:03 = 20080508-0403-cfg_xxxxxxx.sql

-rw-r--r--=A0=A0=A0 1 root=A0=A0=A0=A0 root=A0=A0=A0=A0=A0=A0 = 843960 mag=A0 9 04:03 20080509-0403-cfg_xxxxxxx.sql

 

 

I‘ll try to find it but but even if I can’t provide = this back-up for company policies reason , could I ask you some feed-back to = get suggestion to look for on this back-up file?

 

Many thanx anyway for your help

 

Best Regards

 

Alessandro.

=A0=A0

 

-----Original Message-----
From: Guillaume Lelarge [mailto:guillaume@lelarge.info]
Sent: venerd=EC 9 maggio 2008 19:05
To: MARIOTTI, Alessandro (Alessandro)
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] debug issue on postgresql

 

MARIOTTI, Alessandro (Alessandro) a =E9crit = :

> I’m writing you to get some information regarding the possibility to get

> some information a db corruption got yesterday morning in a = live platform .

>

> We realized DB Inconsistence and corruption and we tried to restore

> immediately the DB , via a back-up procedure, to restore = services for

> customer.

>

> Now we need to investigate on DB what it was the route = cause for db

> corruption.

>

 

Do you have a backup of the corrupted database ? If you don't, = it will

be extremely hard to tell you anything = interesting.

 

And you need to tell us what kind of issue you have, which = release you

use, etc.

 

> Unfortunately we don’t have any experience with = postgres db because the

> platform had improved by a colleague that left company and = no one got

> the opportunity to learn something = …..

>

> Some documentation to start with postgres will be = appreciate .

>

 

http://www.postgresql.org/docs/ and then choose the manual = related to

your PostgreSQL release.

 

Regards.

 

 

--

Guillaume.

=A0 http://www.postgresqlfr.org

=A0 http://dalibo.com

------_=_NextPart_001_01C8B20D.ACEF228F--