it safe to
delete all _copy tables? Should I do any additional housekeeping to
clean this up?
regards
Eliott
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
s the connection specific memory that 8.3
used to need? It seems like that difference is in the (RES-SHR) value.
For 8.2 it is just a few megs, however, in case of 9.2 the non shared
resident portion is 60, sometimes maybe even 100 mb per connection.
regards
eliott
On 2013.12.07. 21:53, Jeff Janes
ach connection process growing to 100mb in memory footprint is
something we haven't experienced with the 8.3.
Of course one solution would be to configure the connection pooler to
expire the connections from time to time, but I am still not convinced
that what we see is normal.
regards
El
the first time
I haven't found anything event remotely resembling our scenario. The
exact version number is: psql (EnterpriseDB) 9.2.1.3
Does anybody have any ideas what causes this?
regards
Eliott
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
ad of time and then, rather than
create them programmatically, just assign them programmatically
instead. It doesn't exactly solve the original problem, but I think i
prefer it from a security standpoint anyhow.
Ben
On 3 Mar 2010, at 09:17, Richard Huxton wrote:
On 02/03/10 18:22,
Sleep often seems a better problem solver than thinking. Create
databases ahead of time and assign at the appropriate time.
Begin forwarded message:
From: Ben Eliott
Date: 2 March 2010 18:22:17 GMT
To: pgsql-general@postgresql.org
Subject: createdb but revoke dropdb
Hi,
In using 8.3. I&#
Hi,
In using 8.3. I'm trying to set up programmatic database creation but
is there a way that the user creating the databases can be restricting
from dropping them?
I have two roles, 'adminuser' with createdb permission, and 'dbuser' a
user with CRUD privileges.
adminuser is a member of
