Hi to all,
After upgrading to 7.1, I have noticed that when doing a vacuum, the
postmaster usually crashes. Noticed also that the available space is 0
bytes free. The pg_xlog directory then contains a large number fo
WAL-files. Tables size are about 7GB for a total database size of over
Hi all,
can somebody explain to me, or point to an
explanation of, the way, PostGreSQL names databases?I have files like 18732 and
7503034 - and they are big but I have no idea which data lives in what
file:
/home/pgsql/data/base/18720/
-rw--- 1 postgres
postgres 70385664 May 24 13:55
Chris Ruprecht wrote:
Hi all,
can somebody explain to me, or point to an explanation of, the way,
PostGreSQL names databases?I have files like 18732 and 7503034 - and
they are big but I have no idea which data lives in what file:
/home/pgsql/data/base/18720/
-rw---1 postgres
Hi, all,
I need your help.
If I config without tcl, compile seems fine.
However, when I config with tcl/tk, I always got some
error, similar case occurs when I tried to install it
via ports.
my OS is FreeBSD4.3 and postgresql-7.1.2, any idea??
I couldn't find tcl.h
I got following when
Jie Liang [EMAIL PROTECTED] writes:
./configure --with-perl --with-tcl --with-tk --with-CXX
--with-setproctitle --with-tclconfig=/usr/local/lib/tcl8.3/
--with-tkconfig=/usr/local/lib/tk8.3/
Looks like you need --with-includes (and probably --with-libs, as well).
tclConfig.sh does not give any
yes, I solved it.
thanks anyway.
Jie LIANG
St. Bernard Software
10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873
[EMAIL PROTECTED]
www.stbernard.com
www.ipinc.com
On Mon, 4 Jun 2001, Tom Lane wrote:
Jie Liang [EMAIL PROTECTED] writes:
./configure --with-perl
Is there a way to limit the number of simultaneous connections that any
given username can make to the database? For instance, I'd like user1 to be
able to have no more than 5 simultaneous connections to the database server,
but user2 can have 15 simultaneous connections.
Also, can these
Peter Eisentraut [EMAIL PROTECTED] writes:
However, this page indicates that there are security risks in doing this.
What are those risks? If I prevent users other than the superuser
postgres from being able to create and drop databases, are there any
security risks?
No. The risks are
Thanks for the feedback!
However, this page indicates that there are security risks in
doing this.
What are those risks? If I prevent users other than the superuser
postgres from being able to create and drop databases, are there any
security risks?
No. The risks are related to the
Tauren Mills [EMAIL PROTECTED] writes:
Is there any way to keep each customer's database within their user area
without the chance of breaking the database server?
If you want completely decoupled service for each user, then give each
of them their own independent installation, running as
10 matches
Mail list logo
