On Sat, 06 Oct 2007 23:05:23 -0700, "Joshua D. Drake"
<[EMAIL PROTECTED]> said:
> Darren Reed wrote:
> > I'm starting to wonder if my database has finally grown too big for my
> > computer.
> >
> > But, rather than peform badly, I see a number of "bad things" happen:
> >
> > * pg_dump fails to ru
On 10/7/07, Darren Reed <[EMAIL PROTECTED]> wrote:
> On Sat, 06 Oct 2007 23:05:23 -0700, "Joshua D. Drake"
> <[EMAIL PROTECTED]> said:
> > Darren Reed wrote:
> > > I'm starting to wonder if my database has finally grown too big for my
> > > computer.
> > >
> > > But, rather than peform badly, I see
On 10/7/07, Darren Reed <[EMAIL PROTECTED]> wrote:
> Scott Marlowe wrote:
> > ...
> >
> > Any reasonably modern version of pgsql should simply stop accepting
> > requests rather than suffering loss due to txid wraparound.So,I can
> > think of two possibilities here. Bad hardware or operator error.
"Darren Reed" <[EMAIL PROTECTED]> writes:
> * pg_dump fails to run, causing an "out of memory" error (I don't
> understand
> why this happens, but it does);
Let's see the exact command to pg_dump and the exact failure message.
It might be useful to add -v so we can get some sense of where in the
Hi,
I've been given the job of creating a hot/warm backup server
for a live Postgresql server. The problem is two-fold: 1) it's version
7.4.9 and an upgrade is not feasible at this time and b) there are
multiple instances of postgresql running on the box; not multiple
databases, multiple *servers
Hi,
I have a corrupt database. I copied the database directory offsite and
restored from a backup. I'm now trying to recover data in the corrupt
database added since the last backup. Any advice on how to approach
this?
It looks like my SAN raid controllers failed (both of them) after
putting in n
Scott Marlowe wrote:
On 10/7/07, Darren Reed <[EMAIL PROTECTED]> wrote:
> Scott Marlowe wrote:
> > ...
> >
> > Any reasonably modern version of pgsql should simply stop accepting
> > requests rather than suffering loss due to txid wraparound.So,I can
> > think of two possibilities here. Bad hardw
On 10/7/07, Darren Reed <[EMAIL PROTECTED]> wrote:
> Scott Marlowe wrote:
> > On 10/7/07, Darren Reed <[EMAIL PROTECTED]> wrote:
> > > Scott Marlowe wrote:
> A few days ago I did:
> pg_dumpall > foo
> What I was doing yesterday was:
> rm -rf /data/db/*
> initdb -D /data/db
> start
> psql < foo
> r
"Faber J. Fedor" <[EMAIL PROTECTED]> writes:
> I've been given the job of creating a hot/warm backup server
> for a live Postgresql server. The problem is two-fold: 1) it's version
> 7.4.9 and an upgrade is not feasible at this time and b) there are
> multiple instances of postgresql running on th
"Mike C" <[EMAIL PROTECTED]> writes:
> I have a corrupt database. I copied the database directory offsite and
> restored from a backup. I'm now trying to recover data in the corrupt
> database added since the last backup. Any advice on how to approach
> this?
If you're lucky, REINDEX might solve y
On 10/8/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Mike C" <[EMAIL PROTECTED]> writes:
> > I have a corrupt database. I copied the database directory offsite and
> > restored from a backup. I'm now trying to recover data in the corrupt
> > database added since the last backup. Any advice on how to
On 10/7/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Faber J. Fedor" <[EMAIL PROTECTED]> writes:
> > I've been given the job of creating a hot/warm backup server
> > for a live Postgresql server. The problem is two-fold: 1) it's version
> > 7.4.9 and an upgrade is not feasible at this time and b) th
"Mike C" <[EMAIL PROTECTED]> writes:
> On 10/8/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>> If you're lucky, REINDEX might solve your problems.
> My problem is that I can't even start postmaster to perform the
> reindex on now. As soon as I try start (via pg_ctl, 8.1.10):
> ...
> postgres_report[24
13 matches
Mail list logo
