Re: encoding names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, peter_e(at)gmx(dot)net, barry(at)xythos(dot)com, zakkr(at)zf(dot)jcu(dot)cz, pgsql-patches(at)postgresql(dot)org
Subject: Re: encoding names
Date: 2001-08-19 15:13:41
Message-ID: 25440.998234021@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> However, this brings up the issue of how a backend will fail if the
> client provides a newer protocol version. I think we should get it to
> send back its current protocol version and see if the client responds
> with a protocol version we can accept.

Why? A client that wants to do this can retry with a lower version
number upon seeing the "unsupported protocol version" failure. There's
no need to change the postmaster code --- indeed, doing so would negate
the main value of such a feature, namely being able to talk to *old*
postmasters.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-08-19 15:22:08 Re: Guide to PostgreSQL source tree
Previous Message Serguei Mokhov 2001-08-19 14:47:03 Re: Guide to PostgreSQL source tree

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2001-08-19 16:28:26 LIKE indexing
Previous Message Tom Lane 2001-08-19 15:11:01 Re: Patch: use SCM_CREDS authentication over PF_LOCAL sockets