| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: Re: pgsql: Fix assorted inconsistencies in GIN opclass support function dec |
| Date: | 2016-05-03 13:32:18 |
| Message-ID: | 19752.1462282338@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> writes:
> On Tue, May 3, 2016 at 12:09 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> It doesn't really matter, though, because there simply isn't any need to
>> refer to these functions from SQL.
> What if we'll want to reuse some on these functions in new opclass?
What context do you imagine that happening in? Surely no other extension
would attempt to re-use them. If, say, hstore itself wanted to reuse
these functions, that would be in a new version of hstore--n.n.sql, so
there's no problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-03 14:44:08 | pgsql: Note that max_worker_processes requires restart. |
| Previous Message | Alexander Korotkov | 2016-05-03 08:32:43 | Re: pgsql: Fix assorted inconsistencies in GIN opclass support function dec |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2016-05-03 13:37:14 | Re: Processes and caches in postgresql |
| Previous Message | Andrew Dunstan | 2016-05-03 13:25:59 | Re: pgindent fixups |