| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, <pgsql-interfaces(at)postgreSQL(dot)org> |
| Subject: | Re: [INTERFACES] Last round (I think) of FE/BE protocol changes |
| Date: | 2003-05-13 22:48:02 |
| Message-ID: | Pine.LNX.4.44.0305140039580.1617-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
Tom Lane writes:
> Let's use int16 (2-byte integers) as format selector codes; this seems a
> reasonable compromise between bandwidth and flexibility. As of 7.4 the
> only supported values will be 0 = text and 1 = binary, but future versions
> can add more codes.
I think the "future versions" in this are going to be making this choice a
datatype-specific session state. How can we make this transition
smoother? Maybe 0 can be default, 1 text, 2 binary? Or maybe we should
implement a simple version of the session-state system right now with only
two predefined transform groups for each type? Then we don't need to send
a format to the server at all, and the messages to the client would
contain an OID field in the RowDescription message.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-13 22:58:18 | Re: [INTERFACES] Last round (I think) of FE/BE protocol changes |
| Previous Message | Peter Eisentraut | 2003-05-13 22:47:46 | Text format protocol representation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-05-13 22:58:18 | Re: [INTERFACES] Last round (I think) of FE/BE protocol changes |
| Previous Message | Agrawal, Manish | 2003-05-08 16:46:54 | Re: Linux equivalent of pgadmin |