| From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Strange behaviour with incompatible psql/server |
| Date: | 2012-11-28 09:46:23 |
| Message-ID: | CABOikdNA5ucOh0y8TkVXmSjZ0Ka8ftCgFXGR8UbxReP3Xa=Evg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 28, 2012 at 2:52 PM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-11-28 10:06:33 | Re: plpgsql_check_function - rebase for 9.3 |
| Previous Message | Pavan Deolasee | 2012-11-28 09:22:34 | Re: Strange behaviour with incompatible psql/server |