Ok I see. So what's the best way to find optimum value for various
memory-related setting of postgresql ?
On Tue, Jan 20, 2009 at 3:27 PM, Albe Laurenz wrote:
> > I wonder how to find how much postgresql memory consumption
> > is (real, not allocated) ?
>
> You could install the pg_buffercache co
Hi all,
I wonder how to find how much postgresql memory consumption is (real, not
allocated) ?
thx.
Hi,
One of my customer's server goes down, I don't know yet how, but when
when they restart the machine I got this:
1. DB is working like usual
2. template0 and template1 database is *duplicated*
3. I can't do pg_dump, because error returned (see below)
How can I backup the database (other than
Hi All,
I've found on pg7.4.x that plpgsql trigger will not wait for finishing
one line of command before executing to the next line, specially if
that command is firing another trigger on another table. This is very
wrong on my point of view. This only happen on pg7. To check:
(create master and
Hi All,
Is there is a way to log every SQL query on potgresql server and also
their execution time?
I need to find which query that eat CPU resource. Applications
connected to this server are from PHP and VB client.
Thanx.
---(end of broadcast)---
... so what if the database size is above 20 GB, do we have to do
pg_dump each at periodics time to get reliable backup?
On 10/11/06, Tom Lane <[EMAIL PROTECTED]> wrote:
Richard Broersma Jr <[EMAIL PROTECTED]> writes:
> I found the correct log file.
> 2006-10-10 04:57:45 PDT% LOG: could not op
Hi All,
All of our application now runs on postgresql7.4.xxx servers, I never
tried it on version 8.xxx
I wonder if there are any guidelines / step by step / special
considerations whether it applies to database structure or the
application it self if we want to upgrade to version 8.xxx ?
Thanks
Hi All,
I try to query on pg_stat_activity but the returned result is only like this:
teramedv2=> select * from pg_stat_activity where datname='teramedv2';
datid | datname | procpid | usesysid | usename | current_query | query_start
---+---+-+--+-+--
So how can we terminate such a long running query ?
The idea is to make a crontab to periodicaly do a job to search a
typical "SELECT * FROM bigtable" query who has run for some hours then
to terminate them...
On 2/9/06, Merlin Moncure <[EMAIL PROTECTED]> wrote:
> > Is there a way to limit user
Hi All,
Is there a way to limit user's CPU resource specially on "SELECT" query ?
I hava a table with a lot of rows inside, if one sloopy DB users do a
"SELECT * FROM bigtable"
then CPU resource will go near 99% and this action will surely affect
the other database performance ...
Thanks.
-
10 matches
Mail list logo