From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unify drop-by-OID functions |
Date: | 2020-05-04 18:57:14 |
Message-ID: | 4e30213d-0ccf-4d95-67f7-f491c8dc5022@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-05-01 17:44, Robert Haas wrote:
> On Fri, May 1, 2020 at 10:51 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> +1
>
> +1 from me, too, but I have a few suggestions:
>
> +DropGenericById(const ObjectAddress *object)
>
> How about "Generic" -> "Object" or "Generic" -> "ObjectAddress"?
Changed to "Object", that also matches existing functions that operate
on an ObjectAddress.
> + elog(ERROR, "cache lookup failed for %s entry %u",
> + elog(ERROR, "could not find tuple for class %u entry %u",
>
> How about "entry" -> "with OID"?
I changed these to just
"cache lookup failed for %s %u"
"could not find tuple for %s %u"
which matches the existing wording for the not-refactored cases. I
don't recall why I went and reworded them.
New patch attached. I'll park it until PG14 opens.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Unify-drop-by-OID-functions.patch | text/plain | 38.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2020-05-04 19:41:45 | Re: design for parallel backup |
Previous Message | Robert Haas | 2020-05-04 18:04:32 | Re: design for parallel backup |