Re: Simplify the logic a bit (src/bin/scripts/reindexdb.c)

From: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Simplify the logic a bit (src/bin/scripts/reindexdb.c)
Date: 2025-02-13 21:38:36
Message-ID: 202502132138.qmsh7ct5itjy@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Feb-13, Ranier Vilela wrote:

> Hi.
>
> Coverity complained about possible dereference null pointer
> in *reindex_one_database* function.
> That's not really true.
> But the logic is unnecessarily complicated.

Hmm, this code looks quite suspect, but I wonder if instead of (what
looks more or less like) a straight revert of cc0e7ebd304a as you
propose, a better fix wouldn't be to split get_parallel_object_list in
two: get_parallel_table_list for the DATABASE and SCHEMA cases, and
get_parallel_tabidx_list (or whatever) for the INDEX case. In the first
case we just return a list of values, but in the latter case we also
meddle with the input list which becomes an output list ...

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
¡Ay, ay, ay! Con lo mucho que yo lo quería (bis)
se fue de mi vera ... se fue para siempre, pa toíta ... pa toíta la vida
¡Ay Camarón! ¡Ay Camarón! (Paco de Lucía)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-02-13 22:18:43 Re: describe special values in GUC descriptions more consistently
Previous Message Nathan Bossart 2025-02-13 21:35:55 Re: DOCS - Question about pg_sequences.last_value notes