pg_restore -N loses extension comment

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: pg_restore -N loses extension comment
Date: 2024-05-07 12:28:58
Message-ID: ZjoeirG7yxODdC4P@pryzbyj2023
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pg_dump -Fc |pg_restore -l -N schema:

| 2; 3079 18187 EXTENSION - pg_buffercache

Without -N schema also shows:

| 2562; 0 0 COMMENT - EXTENSION pg_buffercache

I mean literal s-c-h-e-m-a, but I suppose anything else will work the
same.

BTW, I noticed that pg_restore -v shows that duplicate dependencies can be
stored. We see things like this (and worse).

| 4284; 1259 191439414 VIEW public wmg_server_view telsasoft
| ; depends on: 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 612 23087 612

I see that's possible not only for views, but also tables.
That's probaably wasteful of CPU, at least.

--
Justin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michail Nikolaev 2024-05-07 12:35:13 Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements
Previous Message Justin Pryzby 2024-05-07 12:27:54 Re: bug: copy progress reporting of backends which run multiple COPYs