pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: michael@paquier.xyz
Cc: andres@anarazel.de
Cc: jkatz@postgresql.org
Cc: davecramer@postgres.rocks
Cc: masao.fujii@oss.nttdata.com
Cc: masahiko.sawada@2ndquadrant.com
Cc: sitnikov.vladimir@gmail.com
Cc: pgsql-hackers@postgresql.org
Cc: pg@bowt.ie
Subject: Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762
Date: Wed, 24 Jun 2020 12:50:16 -0400
Message-ID: <20200624165016.GR3125@tamriel.snowman.net> (raw)
In-Reply-To: <20200624145808.GA18120@alvherre.pgsql>
References: <20200624.115638.1224023045303890562.horikyota.ntt@gmail.com>
	<20200624145808.GA18120@alvherre.pgsql>

Greetings,

* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> On 2020-Jun-24, Kyotaro Horiguchi wrote:
> 
> > In logical replication, a replication role is intended to be
> > accessible only to the GRANTed databases.  On the other hand the same
> > role can create a dead copy of the whole cluster, including
> > non-granted databases.
> 
> In other words -- essentially, if you grant replication access to a role
> only to a specific database, they can steal the whole cluster.
> 
> I don't see what's so great about that, but apparently people like it.

Sure, people who aren't in charge of security I'm sure like the ease of
use.

Doesn't mean it makes sense or that we should be supporting that.  What
we should have is a way to allow administrators to configure a system
for exactly what they want to allow, and it doesn't seem like we're
doing that today and therefore we should fix it.  This isn't the only
area we have that issue in.

Thanks,

Stephen

Attachments:

  signature.asc (application/pgp-signature, 818B) download

view thread (44+ messages)  latest in thread

Message-ID: <20200624165016.GR3125@tamriel.snowman.net>
Permalink:  ../20200624165016.GR3125@tamriel.snowman.net/
Also on:    postgresql.org/message-id/20200624165016.GR3125@tamriel.snowman.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: sfrost@snowman.net, alvherre@2ndquadrant.com, horikyota.ntt@gmail.com, michael@paquier.xyz, andres@anarazel.de, jkatz@postgresql.org, davecramer@postgres.rocks, masao.fujii@oss.nttdata.com, masahiko.sawada@2ndquadrant.com, sitnikov.vladimir@gmail.com, pg@bowt.ie
  Subject: Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762
  In-Reply-To: <20200624165016.GR3125@tamriel.snowman.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox