diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-04-07 20:50:02 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-04-07 20:50:02 -0400 |
| commit | 35d1eefb29d03d5a85f71038679f1f8a14358255 (patch) | |
| tree | 8ea18e89f4971e6b3f0a4f57e2f41cd5df0dcb4e /src/backend/parser/parse_utilcmd.c | |
| parent | 6e6b74a206c3b4ad9f22f4910b2e0ed9d922b312 (diff) | |
| download | postgresql-35d1eefb29d03d5a85f71038679f1f8a14358255.tar.gz postgresql-35d1eefb29d03d5a85f71038679f1f8a14358255.zip | |
Fix circle_in to accept "(x,y),r" as it's advertised to do.
Our documentation describes four allowed input syntaxes for circles,
but the regression tests tried only three ... with predictable
consequences. Remarkably, this has been wrong since the circle
datatype was added in 1997, but nobody noticed till now.
David Zhang, with some help from me
Discussion: https://postgr.es/m/332c47fa-d951-7574-b5cc-a8f7f7201202@highgo.ca
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions