From: Andrew Sullivan <ajs@crankycanuck.ca>
To: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Fri, 28 Jan 2005 10:36:20 -0500
Message-ID: <20050128153620.GE9076@phlogiston.dyndns.org> (raw)
In-Reply-To: <1106522910.5790.1.camel@fuji.krosing.net>
References: <200501201503.31241.herve@elma.fr>
<41EFBF05.6000509@familyhealth.com.au>
<200501201536.08656.herve@elma.fr>
<1106236978.35299.496.camel@home>
<1106522910.5790.1.camel@fuji.krosing.net>
On Mon, Jan 24, 2005 at 01:28:29AM +0200, Hannu Krosing wrote:
>
> IIRC it hates pg_dump mainly on master. If you are able to run pg_dump
> from slave, it should be ok.
For the sake of the archives, that's not really a good idea. There
is some work afoot to solve it, but at the moment dumping from a
slave gives you a useless database dump.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
The fact that technology doesn't work is no bar to success in the marketplace.
--Philip Greenspun
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <20050128153620.GE9076@phlogiston.dyndns.org>
* 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