On 03.01.2008, at 05:48, Brian Modra wrote:
I have a pretty "live" table: rows being inserted and updated more
than once 1 per second, though far, far more inserts than updates.
Not that busy ;-)
It has not been vacuumed for months.
Not good.
Now a vacuum on that table takes hours, and I
On 21.03.2007, at 11:25, Karthikeyan Sundaram wrote:
Our database is growing fast. I want to create a cronjob that
should tell me what is the current size of the database on each day.
How can I find this from the database? Is there any pre-written
scripts written by somebody to shar
Hi.
On 9/25/06, Jim Nasby <[EMAIL PROTECTED]> wrote:
As for hardware, until recently, AMD was the un-disputed king when it
came to running PostgreSQL (and databases in general). But the newer
Intel CPUs seem to have surpassed the Opteron. I believe there's a
tweakers.net article floating around
HI.
Can you try (just for testing) using a jdbc2 driver and a connection
string with "protocolVersion=2" included in the jdbc connection?
I had the same issue with this and the problem is, that the query
optimizer sometimes decides NOT to use indexes on prepared statements
(the newer JDBC driver
On 18.08.2006, at 16:14 Uhr, Karen Springer wrote:
I am curious what others out in the community are using as a front-
end to Postgres. We are currently using Microsoft Access & Python
CGI scripts.
We use WebObjects [1] for internal and external applications.
WebObjects and its DirectToWe
On 16.08.2006, at 9:13 Uhr, Soulabaille Samantha wrote:
I've got two databases with the same tables and schema on two
different servers.
I want to have only one database.
Okay.
I don't know how to do this because almost of the tables contains
serial.
And you have overlapping keys from t
On 29.05.2006, at 22:27 Uhr, Peter Kovacs wrote:
Are there any known issues related to compiling for OS X on Intel?
No issues I know about. But I have only build it once on our test
MacBook Pro.
cug
---(end of broadcast)---
TIP 5: don't forg
On 29.05.2006, at 19:56 Uhr, Mitch Pirtle wrote:
Now finally getting comfortable on the new PowerBook, and after weeks
of whining about no OS X packages I discovered the fink binaries,
which I dutifully installed last night.
Bad idea. They are normally old, install in stupid locations, are not
On 17.04.2006, at 5:18 Uhr, Michael Fuhr wrote:
Which way is "better" depends on your access patterns. PostgreSQL
doesn't support cross-database queries (except via functions like
dblink), so if you need to join tables in one database with tables
in another then you'll probably want make A, B,
On 13.04.2006, at 7:56 Uhr, Brendan Duddridge wrote:
What I'd like to see is a table exclusion list. I have a few very
large history tables that are never updated or deleted, only
inserts and selects.
But if you do selects regularly you may want to have the analyse part
of autovacuum for
10 matches
Mail list logo
