pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@libertyrms.info>
To: pgsql-admin@postgresql.org
Subject: Re: postgresql crushed with XLogWrite error
Date: Mon, 05 Jan 2004 16:36:16 -0500
Message-ID: <60k746yt67.fsf@dev6.int.libertyrms.info> (raw)
References: <opr1awxehzjbdarf@localhost>
	<opr1axmnekjbdarf@localhost>
	<20040105134913.GA930@libertyrms.info>
	<opr1a2uws4jbdarf@localhost>
	<20040105140953.GC930@libertyrms.info>
	<opr1a4qaq4jbdarf@localhost>
	<20040105162308.GF930@libertyrms.info>
	<opr1bcg2t7jbdarf@localhost>
	<20040105173920.GO930@libertyrms.info>

andrew@libertyrms.info (Andrew Sullivan) writes:
> On Mon, Jan 05, 2004 at 07:35:16PM +0200, Tsirkin Evgeny wrote:
>> On Mon, 5 Jan 2004 11:23:08 -0500, Andrew Sullivan 
>> <andrew@libertyrms.info> wrote:
>> 
>> I want to keep my configs.Of course i can save my postgresql.conf
>> (and other files that i changed and don't currently remember)
>> to another location and then put it back in place of what rpm will
>> put ,but as i said ,i don't actually remember what i have changed :(
>
> The only things that should make a difference to you should be in the
> /etc directory, assuming the RPM follows the filesystem standard (I
> believe it does).  My suggestion is to back everything up, then
> replace the RPM in the standard way, and then compare the files one
> at a time to see what's different.  I'll bet the binaries and
> libraries, of course, and things under /etc/[postgres?]/, and that's
> it.  Most likely, it'll be postgresql.conf and pg_hba.conf, and maybe
> pg_ident.conf.

It's easy enough to check what files the RPM intends to update...

bash-2.05a$ rpm -q -p -l netpbm-devel-9.24-3.i386.rpm 
/usr/include/pam.h
/usr/include/pammap.h
/usr/include/pbm.h
/usr/include/pbmshhopt.h
/usr/include/pgm.h
/usr/include/pm.h
... other files omitted ...

That can diminish how much is in the "everything" that needs to be
backed up...
-- 
let name="cbbrowne" and tld="libertyrms.info" in String.concat "@" [name;tld];;
<http://dev6.int.libertyrms.com/;
Christopher Browne
(416) 646 3304 x124 (land)



view thread (11+ messages)  latest in thread

Message-ID: <60k746yt67.fsf@dev6.int.libertyrms.info>
Permalink:  ../60k746yt67.fsf@dev6.int.libertyrms.info/
Also on:    postgresql.org/message-id/60k746yt67.fsf@dev6.int.libertyrms.info

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@libertyrms.info
  Subject: Re: postgresql crushed with XLogWrite error
  In-Reply-To: <60k746yt67.fsf@dev6.int.libertyrms.info>
  References: <opr1awxehzjbdarf@localhost> <opr1axmnekjbdarf@localhost> <20040105134913.GA930@libertyrms.info> <opr1a2uws4jbdarf@localhost> <20040105140953.GC930@libertyrms.info> <opr1a4qaq4jbdarf@localhost> <20040105162308.GF930@libertyrms.info> <opr1bcg2t7jbdarf@localhost> <20040105173920.GO930@libertyrms.info> <60k746yt67.fsf@dev6.int.libertyrms.info>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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