Re: pgsql: Fix pg_dump assertion failure when dumping pg_catalog.

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Jeff Davis <jdavis(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix pg_dump assertion failure when dumping pg_catalog.
Date: 2023-08-23 10:24:41
Message-ID: e8bcb3f8-73b8-4761-22df-899cb5f429b1@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 22.08.23 22:08, Jeff Davis wrote:
> Fix pg_dump assertion failure when dumping pg_catalog.
>
> Commit 396d348b04 did not account for the default collation.
>
> Also, use pg_log_warning() instead of Assert().

Looking at this:

pg_log_warning("invalid collation \"%s\"", qcollname);

qcollname is already a quoted identifier, so this message would be
doubly quoted. Maybe you should use collinfo->dobj.name in the messages.

Also, for

pg_fatal("unrecognized collation provider '%c'", collprovider[0]);

use double quotes.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Daniel Gustafsson 2023-08-23 12:19:49 pgsql: doc: Replace list of drivers and PLs with wiki link
Previous Message Peter Eisentraut 2023-08-23 09:28:21 pgsql: doc: Add more ICU rules examples