From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | James William Pye <pgsql(at)jwp(dot)name> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PQ versions request message |
Date: | 2005-09-08 20:27:48 |
Message-ID: | 25446.1126211268@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
James William Pye <pgsql(at)jwp(dot)name> writes:
> The point is to give client authors the ability to authoritatively
> resolve ambiguity that may exist in multiversion supporting clients and
> to do so without any version specific code(or at a minimum wrt older
> servers) or fingerprinting of any sort.
Had we had such a facility from the beginning, it would indeed have that
benefit. But unless you are going to start out by dropping client-side
support for all extant server versions, you will not get any such
benefit; you'll still need retry code. So I still think this isn't
really worth the trouble it would take to implement.
Also, you keep referring to caching the result on the client side and
re-using it across multiple connections --- but you can do that now,
so why is that an argument in favor?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew - Supernews | 2005-09-08 20:29:38 | Re: initdb profiles |
Previous Message | Tom Lane | 2005-09-08 20:14:12 | Re: Attention PL authors: want to be listed in template table? |