Horton
Menu

Re: Strange behaviour with incompatible psql/server

Pavan Deolasee <pavan.deolasee@gmail.com>

View thread
From: Pavan Deolasee <pavan.deolasee@gmail.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-11-28T09:46:23Z
Lists: pgsql-hackers 
On Wed, Nov 28, 2012 at 2:52 PM, Pavan Deolasee <pavan.deolasee@gmail.com>wrote:

>
>
> Should this not be back patched ? The error that's coming because not
> having this fix is rather very strange and hard to debug for any average
> individual. I'd almost concluded that one should NEVER use an old psql with
> a new server even though the warning that comes is not too glaring.
>
>
Never mind. I just read the email thread leading to this commit. This
wasn't a bug fix per se and that's probably the reason why this was never
back patched. The discussion itself looked quite inconclusive as well.

Thanks,
Pavan

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Ignore UTF-8-encoded Unicode byte-order mark at the beginning of a file if