| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-10 23:38:29 |
| Message-ID: | 20140210233829.GA31598@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-02-10 17:35:12 -0600, Merlin Moncure wrote:
> Wrong. You still need to have code that checks the server version and
> see if it's supported (particularly for sending) and as there is *no
> protocol negotiation of the formats at present it's all going to boil
> down to if version = X do Y*. How does the server know which
> 'versions' are ok to send? It doesn't. Follow along with me here:
> Suppose we don't introduce a version flag today and change the format
> to some more exotic structure for 9.5. How has the version flag made
> things easier for the client? It hasn't. The client goes "if version
> = X do Y".
think of binary COPY outputting data in 9.4 and then trying to import
that data into 9.5. That's the interesting case here.
> What about them? Are we now, at the
> upteenth hour of the final commit fest, suddenly deciding that binary
> wire formats going to be compatible across versions?
It has been a concern before.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2014-02-10 23:48:32 | Re: jsonb and nested hstore |
| Previous Message | Merlin Moncure | 2014-02-10 23:35:12 | Re: jsonb and nested hstore |