X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 590B59DD767 for ; Fri, 2 Dec 2005 16:18:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07367-09 for ; Fri, 2 Dec 2005 16:18:05 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by postgresql.org (Postfix) with ESMTP id AC6379DD765 for ; Fri, 2 Dec 2005 16:18:06 -0400 (AST) Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by svr2.postgresql.org (Postfix) with ESMTP id 05BDCF0B1C for ; Fri, 2 Dec 2005 20:18:07 +0000 (GMT) Received: by ns.snowman.net (Postfix, from userid 1000) id A3F5117ADF; Fri, 2 Dec 2005 15:18:47 -0500 (EST) Date: Fri, 2 Dec 2005 15:18:47 -0500 From: Stephen Frost To: Luke Lonergan Cc: David Lang , Steve Oualline , pgsql-performance@postgresql.org Subject: Re: Database restore speed Message-ID: <20051202201847.GE6026@ns.snowman.net> Mail-Followup-To: Luke Lonergan , David Lang , Steve Oualline , pgsql-performance@postgresql.org References: <3E37B936B592014B978C4415F90D662D01C48F01@MI8NYCMAIL06.Mi8.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IWoBo/ZLzY7SPqkS" Content-Disposition: inline In-Reply-To: <3E37B936B592014B978C4415F90D662D01C48F01@MI8NYCMAIL06.Mi8.com> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 15:16:23 up 174 days, 12:28, 8 users, load average: 0.05, 0.16, 0.12 User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/74 X-Sequence-Number: 15895 --IWoBo/ZLzY7SPqkS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Luke Lonergan (LLonergan@greenplum.com) wrote: > > Luke, would it help to have one machine read the file and=20 > > have it connect to postgres on a different machine when doing=20 > > the copy? (I'm thinking that the first machine may be able to=20 > > do a lot of the parseing and conversion, leaving the second=20 > > machine to just worry about doing the writes) >=20 > Unfortunately not - the parsing / conversion core is in the backend, > where it should be IMO because of the need to do the attribute > conversion there in the machine-native representation of the attributes > (int4, float, etc) in addition to having the backend convert from client > encoding (like LATIN1) to the backend encoding (like UNICODE aka UTF8). 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)? The other thought, of course, is that you could use PITR for your backups instead of pgdump... Thanks, Stephen --IWoBo/ZLzY7SPqkS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDkKwnrzgMPqB3kigRAl/AAJ41ewZ4NAWfthI0h/4XvxJc9Sc5ngCfZCyV qvIuwO7f4QS/pR09NHdIyMs= =xGeK -----END PGP SIGNATURE----- --IWoBo/ZLzY7SPqkS--