Re: Dumping security labels for extension owned tables?

From: Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dumping security labels for extension owned tables?
Date: 2022-12-14 20:16:14
Message-ID: CACxu=vJVcSkV-=KkRVb5oz+TSHNVCPutGYMSVGvXWCMeEJRgjw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 14, 2022 at 11:29 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:

>
> Note that if a table is part of an extension, pg_extension_config_dump
> will only lead pg_dump to emit the table data, not the table DDL. The
> table itself must be entirely created by the extension script, and any
> modification done afterwards to a table (or any other object) that is
> part of an extension (a security label but also a comment, new columns
> or anything else) will just be lost. That's how extensions are
> designed, and indeed trying to do inter-extension dependencies like
> this isn't going to work.
>

Ah my bad, sorry for the noise Julien, the create extension statement is
correctly dumped and it applies the label, so I shouldn't have been
expecting the label in the dump (as you informed me). There is some other
root cause for the problem we are observing and we are continuing to dig
into it.

Thank you for your quick reply!

-Michel

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mladen Gogala 2022-12-14 23:53:23 Re: compiling postgres on windows - how to deal with unmatched file extension?
Previous Message Julien Rouhaud 2022-12-14 19:29:34 Re: Dumping security labels for extension owned tables?