Re: [ADMIN] Detecting DB corruption

Am 01.11.2012 06:47, schrieb Craig Ringer: On 11/01/2012 01:10 PM, Scott Ribe wrote: On Oct 31, 2012, at 8:50 PM, Craig Ringer wrote: Seriously, if you're facing DB corruption then something is already horribly wrong with your setup. "Horribly" is not strong enough a word IMHO when we're discu

Re: [ADMIN] Detecting DB corruption

Re-sending to correct addresses. >>Seriously, if you're facing DB corruption then something is already >>horribly wrong with your setup. >"Horribly" is not strong enough a word IMHO when we're discussing double primary key values... except if Raj is not using sequences to generate them. Although

Re: [ADMIN] Public key for wxBase-2.8.12-1.el5.i386.rpm is not installed for pg_admin3

Hi, On Tue, 2012-10-30 at 23:33 +, jkells wrote: > I am trying to install pgadmin3_91.i386 0:1.16.0-1.rhel5 on a centos 5.7 > warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID > 217521f6 > pgdg91/gpgkey | 1.7 kB 00:00 > > > Publ

Re: [ADMIN] Detecting DB corruption

Am 01.11.2012 16:10, schrieb Raj Gandhi: Each DB table has primary key that is populated using DB-sequence. There is a UNIQUE constraint created on natural keys. That does sound decent. The problem on the test setup was because disk cache was enabled. Indexes were corrupted when powering dow

[ADMIN] Fwd: Errors on pg_dumpall

Somebody PLEASE HELP ! is Tome Lane around ! Tks T -- Forwarded message -- From: Terry Khatri Date: 22 October 2012 00:20 Subject: Errors on pg_dumpall To: [email protected] Hi I am getting the following error msg when I do a pg_dumpall - TK@OraLinux /usr/l

Re: [ADMIN] Fwd: Errors on pg_dumpall

You are posting to the wrong list. You should address this in the pgsql-admin list. On Thu, Nov 1, 2012 at 11:05 AM, Terry Khatri wrote: > Somebody PLEASE HELP ! is Tome Lane around ! > Tks > T > > -- Forwarded message -- > From: Te

Re: [ADMIN] Fwd: Errors on pg_dumpall

Oops. You were posting to the right list. I took it for the pgAdmin list. Sorry. :) On Thu, Nov 1, 2012 at 6:06 PM, Fernando Hevia wrote: > You are posting to the wrong list. > You should address this in the > pgsql-admin > list. > > > > > On Thu,