Re: security labels on databases are bad for dump & restore

From: Andres Freund <andres(at)anarazel(dot)de>
To: Adam Brightwell <adam(dot)brightwell(at)crunchydatasolutions(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Subject: Re: security labels on databases are bad for dump & restore
Date: 2015-07-15 08:18:41
Message-ID: 20150715081840.GC5520@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-07-14 13:09:26 -0400, Adam Brightwell wrote:
> All,
>
> >> I won't have time to do anything about this anytime soon, but I think we
> >> should fix that at some point. Shall I put this on the todo? Or do we
> >> want to create an 'open items' page that's not major version specific?
> >
> > I think adding it to the TODO would be great.

Done. It's rather telling that it took me a fair while to find a spot in
the todo list where it fits...

> I'd be willing to look/dive into this one further.

Cool.

One thing worth mentioning is that arguably the problem is caused by the
fact that we're here emitting database level information in pg_dump,
normally only done for dumpall.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-07-15 08:24:24 Re: [DESIGN] Incremental checksums
Previous Message Yourfriend 2015-07-15 08:10:10 Re: Could be improved point of UPSERT