From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, michael(dot)paquier(at)gmail(dot)com |
Subject: | Re: Issue in pg_catalog.pg_indexes view definition |
Date: | 2016-07-14 18:20:24 |
Message-ID: | 9810.1468520424@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andreas Seltenreich <seltenreich(at)gmx(dot)de> writes:
> Tom Lane writes:
>> We've dealt with similar issues in places like pg_relation_size() by
>> making the functions return NULL instead of throwing an error for an
>> unmatched argument OID.
> Note that Michael Paquier sent a patch implementing this in another
> thread:
> https://www.postgresql.org/message-id/CAB7nPqTxF5dtxjEzB7xkJvOWxX8D_2atxmTu3PSnkhcWT_JY5A@mail.gmail.com
Ah, I had a feeling that this had come up recently, but failed to remember
that there was already a patch. Maybe we should just bump up the priority
of reviewing that patch.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-07-14 18:27:20 | Re: pg_xlogdump follow into the future |
Previous Message | Andres Freund | 2016-07-14 18:17:10 | Re: Improving executor performance |