| From: | Mitch Skinner <mitch(at)egcrc(dot)net> |
|---|---|
| To: | Luke Lonergan <llonergan(at)greenplum(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, David Lang <dlang(at)invendra(dot)net>, Steve Oualline <soualline(at)stbernard(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Database restore speed |
| Date: | 2005-12-03 03:26:06 |
| Message-ID: | 1133580366.3367.123.camel@enzian |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luke Lonergan | 2005-12-03 04:03:57 | Re: Database restore speed |
| Previous Message | Francisco Reyes | 2005-12-02 23:28:09 | Small table or partial index? |