| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jean-Pierre Pelletier <jean(dot)pierre(dot)pelletier0(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Out arguments name of "pg_identify_object_as_address" function in 9.5.14 and 11beta3 |
| Date: | 2018-09-05 15:57:11 |
| Message-ID: | 20180905155711.ddnezdeqcraew5h6@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Sep-05, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > That said, I haven't heard of anyone using these functions in code yet,
> > so if we change it in 11 or 12 nobody is going to complain.
>
> ... and that's pretty much my feeling. It seems really unlikely that
> anyone's using named-argument notation for pg_get_object_address, and
> even if they are, it wouldn't be very painful to change, or just not
> use the notation if they need cross-branch compatibility. I think it's
> more useful in the long run to make the names consistent.
>
> Will go take care of it.
Agreed, thanks. If you haven't touched the docs yet, here's the change
-- 9.5/9.6/10 need a slight adjustment from 11/master.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| docs-11.patch | text/plain | 1.6 KB |
| docs-96.patch | text/plain | 1.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-09-05 16:23:37 | Re: Prevent concurrent DROP SCHEMA when certain objects are being initially created in the namespace |
| Previous Message | Tom Lane | 2018-09-05 15:49:36 | Re: Out arguments name of "pg_identify_object_as_address" function in 9.5.14 and 11beta3 |