Re: pg_dump and BINARY mode COPY

From: Hubert FONGARNAND <informatique(dot)internet(at)fiducial(dot)fr>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump and BINARY mode COPY
Date: 2007-12-07 12:40:40
Message-ID: 1197031240.11519.25.camel@hublinux.fidudev.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I use often pgdump... and we have many bytea on our database...
Without binary COPY, backup is very slow and takes 4x more space on the
network wire...

It would be great to have an option (--binary) with eventually a WARNING
message (that your backup could be not portable across architecture...)
but i think that 99% of the time we don't change between x86 or ppc....

please think for users...
Hubert

Le jeudi 06 décembre 2007 à 18:32 +0000, Simon Riggs a écrit :

> On Thu, 2007-12-06 at 13:22 -0500, Tom Lane wrote:
> > Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > > On Thu, 2007-12-06 at 12:43 -0500, Tom Lane wrote:
> > >> To preserve platform and version independence of the dump.
> >
> > > Only if there is a risk. Since a common route to upgrade is a
> > > dump/restore back onto same box it seems worth having an option to do
> > > this.
> >
> > I think you missed the point about version independence. That would be
> > exactly the scenario where a version-to-version change in binary format
> > --- for instance, "money" widening to 64 bits in 8.3 --- would burn you.
>
> OK
>
> > Furthermore, this doesn't seem like a scenario where performance ought
> > to be the primary concern. How often do you do major version upgrades?
>
> Not often enough.
>
> If it was faster, we would rely on more people actually doing it.
>

_________________________________________________
Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.
Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.
Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-12-07 12:49:33 Re: Problem with ControlFileData structure being ABI depe ndent
Previous Message Trevor Talbot 2007-12-07 12:19:53 Re: Problem with ControlFileData structure being ABI dependent