pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Luke Lonergan <llonergan@greenplum.com>
Cc: David Lang <dlang@invendra.net>
Cc: Steve Oualline <soualline@stbernard.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Database restore speed
Date: Fri, 2 Dec 2005 16:19:25 -0500
Message-ID: <20051202211925.GF6026@ns.snowman.net> (raw)
In-Reply-To: <BFB5F308.14E82%llonergan@greenplum.com>
References: <20051202201847.GE6026@ns.snowman.net>
	<BFB5F308.14E82%llonergan@greenplum.com>

* Luke Lonergan (llonergan@greenplum.com) wrote:
> On 12/2/05 12:18 PM, "Stephen Frost" <sfrost@snowman.net> wrote:
> > Just a thought, but couldn't psql be made to use the binary mode of
> > libpq and do at least some of the conversion on the client side?  Or
> > does binary mode not work with copy (that wouldn't suprise me, but
> > perhaps copy could be made to support it)?
> 
> Yes - I think this idea is implicit in what David suggested, and my response
> as well.  The problem is that the way the client does conversions can
> potentially differ from the way the backend does.  Some of the types in
> Postgres are machine intrinsic and the encoding conversions use on-machine
> libraries, each of which preclude the use of client conversion methods
> (without a lot of restructuring).  We'd tackled this problem in the past and
> concluded that the parse / convert stage really belongs in the backend.

I've used the binary mode stuff before, sure, Postgres may have to
convert some things but I have a hard time believing it'd be more
expensive to do a network_encoding -> host_encoding (or toasting, or
whatever) than to do the ascii -> binary change.

	Thanks,

		Stephen

Attachments:

  signature.asc (application/pgp-signature, 188B) download

view thread (25+ messages)  latest in thread

Message-ID: <20051202211925.GF6026@ns.snowman.net>
Permalink:  ../20051202211925.GF6026@ns.snowman.net/
Also on:    postgresql.org/message-id/20051202211925.GF6026@ns.snowman.net

 · 

reply

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: sfrost@snowman.net, llonergan@greenplum.com, dlang@invendra.net, soualline@stbernard.com
  Subject: Re: Database restore speed
  In-Reply-To: <20051202211925.GF6026@ns.snowman.net>

* 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