Re: Issue in pg_catalog.pg_indexes view definition

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Issue in pg_catalog.pg_indexes view definition
Date: 2016-07-14 08:15:46
Message-ID: a96421bd-5842-0000-7a76-c23502a55640@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016/07/14 17:07, Amit Langote wrote:
> Can we say that pg_get_indexdef() has "side-effects" because it can error
> like this? Shouldn't such a function be marked *volatile*? Because if I
> do so by updating pg_proc, the plan changes (perhaps) to a safe one in
> this context:

Didn't mean to write: "Because if I do so..."

Instead: "If I do so..."

Thanks,
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2016-07-14 08:21:07 Re: unexpected psql "feature"
Previous Message Michael Paquier 2016-07-14 08:10:09 Re: Issue in pg_catalog.pg_indexes view definition