pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Postgres hackers <pgsql-hackers@postgresql.org>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Subject: Re: pg_partition_tree crashes for a non-defined relation
Date: Mon, 10 Dec 2018 07:39:41 +0900
Message-ID: <20181209223941.GA3710@paquier.xyz> (raw)
In-Reply-To: <19520.1544382449@sss.pgh.pa.us>
References: <20181207010406.GO2407@paquier.xyz>
	<20181207230540.GA12740@paquier.xyz>
	<6105.1544243612@sss.pgh.pa.us>
	<20181208065436.GC1989@paquier.xyz>
	<20181208134608.GY3415@tamriel.snowman.net>
	<20181208231507.GA1833@paquier.xyz>
	<20181209174815.GD3415@tamriel.snowman.net>
	<16590.1544378743@sss.pgh.pa.us>
	<20181209185452.GF3415@tamriel.snowman.net>
	<19520.1544382449@sss.pgh.pa.us>

On Sun, Dec 09, 2018 at 02:07:29PM -0500, Tom Lane wrote:
> Stephen Frost <sfrost@snowman.net> writes:
>> I don't entirely buy off on the argument that it's code that's 'highly
>> unlikely to break once written' though- we do add new relkinds from time
>> to time, for example.  Perhaps we could have these functions run just
>> once per relkind.
> 
> Well, the relevant code is likely to be "if relkind is not x, y, or z,
> then PG_RETURN_NULL".  If we add a new relkind and forget to consider the
> function, the outcome is a NULL result that perhaps should not have been
> NULL ... but a test like this won't help us notice that.

Yes, in order to prevent problems with newly-introduced relkinds, I
think that the checks within functions should be careful to check only
for relkinds that they support, and not list those they do not support.
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (36+ messages)  latest in thread

Message-ID: <20181209223941.GA3710@paquier.xyz>
Permalink:  ../20181209223941.GA3710@paquier.xyz/
Also on:    postgresql.org/message-id/20181209223941.GA3710@paquier.xyz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: michael@paquier.xyz, tgl@sss.pgh.pa.us, sfrost@snowman.net, Langote_Amit_f8@lab.ntt.co.jp
  Subject: Re: pg_partition_tree crashes for a non-defined relation
  In-Reply-To: <20181209223941.GA3710@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox