From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: Lee Wu <Lwu@mxlogic.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump, pg_restore, insert vs copy
Date: Thu, 24 Mar 2005 11:51:08 -0500
Message-ID: <27632.1111683068@sss.pgh.pa.us> (raw)
In-Reply-To: <20050324164433.GA8068@dcc.uchile.cl>
References: <ECAB83AA52BCC043A0E24BBC00001024D2E6BC@mxhq-exch.corp.mxlogic.com>
<27059.1111679526@sss.pgh.pa.us>
<20050324164433.GA8068@dcc.uchile.cl>
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> Is there any reason why we don't use a binary storage in custom format
> dumps? I mean, we could open a binary cursor and write the results to
> the file, and read it back at restore time. This is just handwaving of
> course.
> I guess the reason is cross-version portability?
Cross-platform portability, too.
regards, tom lane
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: tgl@sss.pgh.pa.us, alvherre@dcc.uchile.cl, Lwu@mxlogic.com
Subject: Re: pg_dump, pg_restore, insert vs copy
In-Reply-To: <27632.1111683068@sss.pgh.pa.us>
References: <ECAB83AA52BCC043A0E24BBC00001024D2E6BC@mxhq-exch.corp.mxlogic.com> <27059.1111679526@sss.pgh.pa.us> <20050324164433.GA8068@dcc.uchile.cl> <27632.1111683068@sss.pgh.pa.us>
* 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