|From:||Andres Freund <andres(at)anarazel(dot)de>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Subject:||Re: Is it time to kill support for very old servers?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Re-upping this topic.
On 2016-10-07 10:06:07 -0400, Tom Lane wrote:
> In the same line, maybe we should kill libpq's support for V2 protocol
> (which would make the cutoff 7.4). And maybe the server's support too,
> though that wouldn't save very much code. The argument for cutting this
> isn't so much that we would remove lots of code as that we're removing
> code that never gets tested, at least not by us.
I'd like to do this in the not too far away future for at least the
backend. There's enough not particularly pretty code to deal with v2
that that'd be worthwhile.
> One small problem with cutting libpq's V2 support is that the server's
> report_fork_failure_to_client() function still sends a V2-style message.
> We could change that in HEAD, certainly, but we don't really want modern
> libpq unable to parse such a message from an older server. Possibly we
> could handle that specific case with a little special-purpose code and
> still be able to take out most of fe-protocol2.c.
We should really fix that so it reports the error as a v3 message,
independent of ripping out libpq-fe support for v2.
|Next Message||Robert Haas||2017-09-14 00:20:48||Re: Race between SELECT and ALTER TABLE NO INHERIT|
|Previous Message||Robert Haas||2017-09-14 00:15:13||Re: generated columns|