pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
debug issue on postgresql 4+ messages / 2 participants [nested] [flat]
* debug issue on postgresql @ 2008-05-09 14:34 MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> 2008-05-09 17:04 ` Re: debug issue on postgresql Guillaume Lelarge <guillaume@lelarge.info> 0 siblings, 1 reply; 4+ messages in thread From: MARIOTTI, Alessandro \(Alessandro\) @ 2008-05-09 14:34 UTC (permalink / raw) To: pgsql-admin Hi All, 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. 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 . Best Regards Alessandro. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: debug issue on postgresql 2008-05-09 14:34 debug issue on postgresql MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> @ 2008-05-09 17:04 ` Guillaume Lelarge <guillaume@lelarge.info> 2008-05-09 19:48 ` Re: debug issue on postgresql MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> 0 siblings, 1 reply; 4+ messages in thread From: Guillaume Lelarge @ 2008-05-09 17:04 UTC (permalink / raw) To: MARIOTTI, Alessandro \(Alessandro\) <mariotti@alcatel-lucent.com>; +Cc: pgsql-admin MARIOTTI, Alessandro (Alessandro) a écrit : > 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. http://www.postgresqlfr.org http://dalibo.com ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: debug issue on postgresql 2008-05-09 14:34 debug issue on postgresql MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> 2008-05-09 17:04 ` Re: debug issue on postgresql Guillaume Lelarge <guillaume@lelarge.info> @ 2008-05-09 19:48 ` MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> 2008-05-09 23:07 ` Re: debug issue on postgresql Guillaume Lelarge <guillaume@lelarge.info> 0 siblings, 1 reply; 4+ messages in thread From: MARIOTTI, Alessandro \(Alessandro\) @ 2008-05-09 19:48 UTC (permalink / raw) To: Guillaume Lelarge <guillaume@lelarge.info>; +Cc: pgsql-admin 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 "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 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 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. -----Original Message----- From: Guillaume Lelarge [mailto:guillaume@lelarge.info] Sent: venerdì 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 écrit : > 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. http://www.postgresqlfr.org http://dalibo.com ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: debug issue on postgresql 2008-05-09 14:34 debug issue on postgresql MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> 2008-05-09 17:04 ` Re: debug issue on postgresql Guillaume Lelarge <guillaume@lelarge.info> 2008-05-09 19:48 ` Re: debug issue on postgresql MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> @ 2008-05-09 23:07 ` Guillaume Lelarge <guillaume@lelarge.info> 0 siblings, 0 replies; 4+ messages in thread From: Guillaume Lelarge @ 2008-05-09 23:07 UTC (permalink / raw) To: MARIOTTI, Alessandro \(Alessandro\) <mariotti@alcatel-lucent.com>; +Cc: pgsql-admin MARIOTTI, Alessandro (Alessandro) a écrit : > 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; > None of these could have caused a corruption. > 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 . > > Now they asking us what’s happen so this is the reason why I’m writing > here . > You'll need more info if you want to find out what happened. > Unfortunately I tried to verify the backup db but the one interesting > for us is empty : > > 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 > You don't a SQL backup, these won't help you. You need a backup of the database after the corruption. > 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? > Nope. You didn't give us enough information to at least get started. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2008-05-09 23:07 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2008-05-09 14:34 debug issue on postgresql MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> 2008-05-09 17:04 ` Guillaume Lelarge <guillaume@lelarge.info> 2008-05-09 19:48 ` MARIOTTI, Alessandro (Alessandro) <mariotti@alcatel-lucent.com> 2008-05-09 23:07 ` Guillaume Lelarge <guillaume@lelarge.info>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox