Re: Bloated pg_shdepend_depender_index

From: "Andy Shellam" <andy(dot)shellam(at)mailnetwork(dot)co(dot)uk>
To: "'Jim C(dot) Nasby'" <jnasby(at)pervasive(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Bloated pg_shdepend_depender_index
Date: 2006-03-29 12:16:13
Message-ID: !&!AAAAAAAAAAAuAAAAAAAAALfqleqaijxJlxu+E5RYF+YBAJaQ0jfg6zBFp7poaER6UCkAAAGy3PcAABAAAABny9p8KUNnSIk/ZFDeNe+NAQAAAAA=@mailnetwork.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

This is true, but you could run the new version on the same server/different
port to the current version, and do a simultaneous dump/restore without
having to use extra disk space, or taking your production database offline -
then you can schedule a time to kill the old one, re-assign the port on the
new one and bring it up - would take about 30 seconds, and this could be
done at a time when traffic was at its lowest.

QUOTE:
Uh, for many sites minutes of downtime would be a huge issue, let alone
hours.

Fortunately, you can use Slony to migrate between versions, greatly
reducing downtime.
END QUOTE

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andy Shellam 2006-03-29 12:19:02 Re: FW: Setting up of PITR system.
Previous Message Gourish Singbal 2006-03-29 10:06:36 auto vacuuming