From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Wainaina <petwah17@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: RESTRICT TABLE OWNER NOT TO DELETE IT
In-reply-to: 
 <CAEEbwbfqg-xForZePcXDeuvP0mUWMRO6ys0ot_2rnhor6Ogppg@mail.gmail.com>
References: 
 <CAEEbwbfqg-xForZePcXDeuvP0mUWMRO6ys0ot_2rnhor6Ogppg@mail.gmail.com>
Comments: In-reply-to Peter Wainaina <petwah17@gmail.com>
	message dated "Mon, 08 Mar 2021 14:23:43 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1741402.1615219092.1@sss.pgh.pa.us>
Date: Mon, 08 Mar 2021 10:58:12 -0500
Message-ID: <1741403.1615219092@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1741403.1615219092%40sss.pgh.pa.us>
Precedence: bulk

Peter Wainaina <petwah17@gmail.com> writes:
> i need help on how to restrict the table owner no to drop/truncate the table

As far as Postgres is concerned, "can drop the object" is pretty much
the definition of ownership.  Maybe you need to rethink who owns which
tables in your design.  (Yes, you could use event triggers to interfere
with the normal system behavior, but that doesn't make it a good idea.)

The owner can revoke her own TRUNCATE privilege, but that's just a
mistake preventer, since she can also re-grant the privilege to herself.

			regards, tom lane