| From: | "Matthew Dennis" <mdennis(at)merfer(dot)net> |
|---|---|
| To: | Christophe <xof(at)thebuild(dot)com> |
| Cc: | PGSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: indexes on functions and create or replace function |
| Date: | 2008-08-29 00:49:16 |
| Message-ID: | e94d85500808281749p52edb592q914f23baefa1ec93@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Aug 28, 2008 at 5:32 PM, Christophe <xof(at)thebuild(dot)com> wrote:
> On Aug 28, 2008, at 3:21 PM, Matthew Dennis wrote:
>
>> I have no doubt that someone would complain about it, but I think it's
>> better than the alternative.
>>
>
> Determining if changing any function will cause an index to break is not a
> straight-forward problem. I don't believe that PG right now keeps a graph
> of which functions call which, so replacing a function deep in the logical
> calling hierarchy could break the index as easily as one mentioned at the
> top.
>
Yes, I can see that would indeed be a problem. Are there future plans to
start tracking such dependencies? It seems like it would be a good idea in
general.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe | 2008-08-29 00:52:45 | Re: indexes on functions and create or replace function |
| Previous Message | Matthew Dennis | 2008-08-29 00:45:00 | Re: indexes on functions and create or replace function |