On Sun, 2012-12-02 at 10:32 +0530, Pavan Deolasee wrote:
On Sun, Dec 2, 2012 at 7:53 AM, Edson Richter edsonrich...@hotmail.comwrote:
Em 01/12/2012 22:22, Chris Angelico escreveu:
On Sun, Dec 2, 2012 at 10:20 AM, Edson Richter edsonrich...@hotmail.com
wrote:
I've put both files in
Em 02/12/2012 07:53, Guillaume Lelarge escreveu:
On Sun, 2012-12-02 at 10:32 +0530, Pavan Deolasee wrote:
On Sun, Dec 2, 2012 at 7:53 AM, Edson Richter edsonrich...@hotmail.comwrote:
Em 01/12/2012 22:22, Chris Angelico escreveu:
On Sun, Dec 2, 2012 at 10:20 AM, Edson Richter
On Sun, 2012-12-02 at 08:09 -0200, Edson Richter wrote:
Em 02/12/2012 07:53, Guillaume Lelarge escreveu:
On Sun, 2012-12-02 at 10:32 +0530, Pavan Deolasee wrote:
On Sun, Dec 2, 2012 at 7:53 AM, Edson Richter
edsonrich...@hotmail.comwrote:
Em 01/12/2012 22:22, Chris Angelico escreveu:
Em 23/11/2012 19:18, Guillaume Lelarge escreveu:
On Fri, 2012-11-09 at 09:19 -0200, Edson Richter wrote:
I've a bunch of databases that cannot be dropped in any case.
I was wondering if it is possible to revoke drop database permission
for all users, in order that even superuser, if he wishes
On Sun, Dec 2, 2012 at 10:20 AM, Edson Richter edsonrich...@hotmail.com wrote:
I've put both files in ~/deny_drop folder, and executed make:
# LANG=C make
Makefile:13: ../../src/Makefile.global: No such file or directory
Makefile:14: /contrib/contrib-global.mk: No such file or directory
Em 01/12/2012 22:22, Chris Angelico escreveu:
On Sun, Dec 2, 2012 at 10:20 AM, Edson Richter edsonrich...@hotmail.com wrote:
I've put both files in ~/deny_drop folder, and executed make:
# LANG=C make
Makefile:13: ../../src/Makefile.global: No such file or directory
Makefile:14:
On Sun, Dec 2, 2012 at 7:53 AM, Edson Richter edsonrich...@hotmail.comwrote:
Em 01/12/2012 22:22, Chris Angelico escreveu:
On Sun, Dec 2, 2012 at 10:20 AM, Edson Richter edsonrich...@hotmail.com
wrote:
I've put both files in ~/deny_drop folder, and executed make:
# LANG=C make
On Fri, 2012-11-23 at 23:56 -0200, Edson Richter wrote:
Wordeful!
Guillaume, Thanks.
Ill give a try for few weeks in the development and test databases
before put in production.
Make sure you test it thoroughly. As I said, it's more an example code,
than a production-ready code.
If
On Fri, 2012-11-09 at 09:19 -0200, Edson Richter wrote:
I've a bunch of databases that cannot be dropped in any case.
I was wondering if it is possible to revoke drop database permission
for all users, in order that even superuser, if he wishes to drop a
database, he will need first to
Wordeful!
Guillaume, Thanks.
I"ll give a try for few weeks in the development and test
databases before put in production.
Regards,
Edson Carlos Ericksson Richter
I've a bunch of databases that cannot be dropped in any case.
I was wondering if it is possible to revoke "drop database"
permission for all users, in order that even superuser, if he wishes
to drop a database, he will need first to "grant drop database"
first.
Edson Richter wrote:
I've a bunch of databases that cannot be dropped in any case.
I was wondering if it is possible to revoke drop database permission
for all users, in order that
even superuser, if he wishes to drop a database, he will need first to
grant drop database first.
I know
Thanks, this is exactly what I was
looking for.
One more question: changing this attribute will present is no side
effects?
Thanks,
Edson Carlos Ericksson Richter
On 2012-11-09 12:42:37 +0100, Albe Laurenz wrote:
Edson Richter wrote:
I've a bunch of databases that cannot be dropped in any case.
I was wondering if it is possible to revoke drop database permission
for all users, in order that
even superuser, if he wishes to drop a database, he will
Andres Freund and...@anarazel.de writes:
On 2012-11-09 12:42:37 +0100, Albe Laurenz wrote:
You cannot play it over permissions, but what about the following trick:
postgres=# CREATE DATABASE persist;
CREATE DATABASE
postgres=# UPDATE pg_database SET datistemplate=TRUE WHERE
Em 09/11/2012 20:18, Tom Lane escreveu:
Andres Freund and...@anarazel.de writes:
On 2012-11-09 12:42:37 +0100, Albe Laurenz wrote:
You cannot play it over permissions, but what about the following trick:
postgres=# CREATE DATABASE persist;
CREATE DATABASE
postgres=# UPDATE pg_database SET
16 matches
Mail list logo
