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 431579DD70A for ; Fri, 2 Dec 2005 23:26:02 -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 70623-07 for ; Fri, 2 Dec 2005 23:25:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail2.egcrc.net (63-193-204-9.egcrc.org [63.193.204.9]) by postgresql.org (Postfix) with ESMTP id C08889DCAD7 for ; Fri, 2 Dec 2005 23:25:58 -0400 (AST) Received: from egcrc-ex01.egcrc.org ([172.16.1.4]) by mail2.egcrc.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 2 Dec 2005 19:26:02 -0800 Received: from 172.16.0.166 ([172.16.0.166]) by egcrc-ex01.egcrc.org ([172.16.1.4]) with Microsoft Exchange Server HTTP-DAV ; Sat, 3 Dec 2005 03:26:02 +0000 Received: from enzian by egcrc-ex01.egcrc.org; 02 Dec 2005 19:26:06 -0800 Subject: Re: Database restore speed From: Mitch Skinner To: Luke Lonergan Cc: Stephen Frost , David Lang , Steve Oualline , pgsql-performance@postgresql.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 02 Dec 2005 19:26:06 -0800 Message-Id: <1133580366.3367.123.camel@enzian> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) X-OriginalArrivalTime: 03 Dec 2005 03:26:02.0677 (UTC) FILETIME=[49A94E50:01C5F7B9] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200512/89 X-Sequence-Number: 15910 On Fri, 2005-12-02 at 13:24 -0800, Luke Lonergan wrote: > It's a matter of safety and generality - in general you > can't be sure that client machines / OS'es will render the same conversions > that the backend does in all cases IMO. Can't binary values can safely be sent cross-platform in DataRow messages? At least from my ignorant, cursory look at printtup.c, there's a binary format code path. float4send in utils/adt/float.c uses pq_sendfloat4. I obviously haven't followed the entire rabbit trail, but it seems like it happens. IOW, why isn't there a cross-platform issue when sending binary data from the backend to the client in query results? And if there isn't a problem there, why can't binary data be sent from the client to the backend? Mitch