Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-08-19 15:22:08
Subject: Re: Guide to PostgreSQL source tree
Previous:From: Serguei MokhovDate: 2001-08-19 14:47:03
Subject: Re: Guide to PostgreSQL source tree

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group