pg_restore -N loses extension comment - Mailing list pgsql-hackers

From Justin Pryzby
Subject pg_restore -N loses extension comment
Date
Msg-id ZjoeirG7yxODdC4P@pryzbyj2023
Whole thread Raw
Responses Re: pg_restore -N loses extension comment
List 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
612612 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
612612 23087 612
 

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

-- 
Justin



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: bug: copy progress reporting of backends which run multiple COPYs
Next
From: Michail Nikolaev
Date:
Subject: Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements