| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: unexpected psql "feature" |
| Date: | 2016-07-14 10:38:51 |
| Message-ID: | CAEzk6fdgFP+_U-CHgjCxzV56uGKk4kojXbJQmjp0CgHyquerqw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14 July 2016 at 00:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wonder
> whether promoting \; to a recognized and documented behavior would
> allow us to get away with converting -c strings to normal parsing
> behavior, as was discussed and then rejected on compatibility grounds
> not too long ago. People who need to keep the old behavior could do so
> by putting in backslashes.
>
Just so I'm clear: you're suggesting that
because people can modify their code to achieve the old behaviour it's no
longer breaking compatibility?
That's an odd definition, IMO.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-07-14 11:03:47 | Re: Hash Indexes |
| Previous Message | Kenan Yao | 2016-07-14 09:53:40 | Hang issue when COPY to/from an unopened FIFO |