From: Sean Chittenden <sean@chittenden.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Barry Lind <blind@xythos.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Wed, 12 Mar 2003 23:04:35 -0800
Message-ID: <20030313070435.GC79234@perrin.int.nxad.com> (raw)
In-Reply-To: <27307.1047485980@sss.pgh.pa.us>
References: <19041.1047322279@sss.pgh.pa.us>
<3E6EEA9B.3050201@xythos.com>
<27307.1047485980@sss.pgh.pa.us>
> > One addition I would personally like to see (it comes up in my
> > apps code) is the ability to detect wheather the server is big
> > endian or little endian. When using binary cursors this is
> > necessary in order to read int data.
>
> Actually, my hope is to eliminate that business entirely by
> standardizing the on-the-wire representation for binary data; note
> the reference to send/receive routines in the original message. For
> integer data this is simple enough: network byte order will be it.
> I'm not sure yet what to do about float data.
When were talking sending data across the wire, are we talking about a
format that would let the server use sendfile() for sending the data
to the client? Having a database that can send data to the client
efficiently would be a nice change of pace given most databases since
RDBMSs are notoriously slow (slower than NFS) at sending files to
clients. -sc
--
Sean Chittenden
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-interfaces@postgresql.org
Cc: sean@chittenden.org, tgl@sss.pgh.pa.us, blind@xythos.com, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
In-Reply-To: <20030313070435.GC79234@perrin.int.nxad.com>
* 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